Emmanuel Kala
08/21/2026, 7:28 PMkapa.ai
08/21/2026, 7:28 PMairbyte.syncs, airbyte.gb_moved, airbyte.sync_duration, and airbyte.api_requests — require global.edition: enterprise. Community deployments do not emit these metrics. [Discussion]
Additionally, while the Helm chart V2 does render the global.metrics.statsd.* / otlp.collectorEndpoint environment variables, metric emission itself is gated behind the Enterprise edition check — so setting these values on Community will have no effect. [Discussion]
The legacy DogStatsD path (METRIC_CLIENT=datadog) is also Enterprise-only as of v1.5.0, and is only supported on legacy Docker deployments (not Kubernetes/abctl). [GitHub Issue]
For Community deployments, your main options for monitoring are:
1. Querying the metadata DB directly — using the jobs, attempts, and normalization_summaries tables. Airbyte publishes a Database Data Catalog documenting this schema, though it does not carry explicit stability guarantees across versions.
2. Polling the Airbyte API — the /api/public/v1/ endpoints are available on Community and include job status information, making it a more stable interface than direct DB queries. [Discussion] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.