Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> how to enable metrics for airbyte oss?

*Enabling Metrics for Airbyte OSS*
For Airbyte OSS (open-source), you can enable metrics reporting using environment variables. The key variables are:
• *`PUBLISH_METRICS`* – Set to `true` to enable metrics publishing. Defaults to `false`.
• *`METRIC_CLIENT`* – Specifies which metrics client to use. Accepts either `datadog` or `otel`. Only relevant when `PUBLISH_METRICS` is `true`.
[<https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#monitoring|Configuring Airbyte - Monitoring>]
-------------------------
*Option 1: OpenTelemetry (OTel)*
Set the following environment variables:
• `METRIC_CLIENT=otel`
• `OTEL_COLLECTOR_ENDPOINT=<ip:port>` – The endpoint the OTel metric client sends metrics to.
You also need to deploy an `airbyte-metrics` service. For example, in Docker Compose:
```airbyte-metrics:
  image: airbyte/metrics-reporter:${VERSION}
  container_name: airbyte-metrics
  environment:
    - METRIC_CLIENT=${METRIC_CLIENT}
    - OTEL_COLLECTOR_ENDPOINT=${OTEL_COLLECTOR_ENDPOINT}
```
Your OpenTelemetry collector must accept OTLP over HTTP. A minimal collector config:
```receivers:
  otlp:
    protocols:
      http:
        endpoint: 0.0.0.0:4318
```
[<https://docs.airbyte.com/platform/1.7/operator-guides/collecting-metrics|Collecting Metrics - 1.7>]
-------------------------
*Option 2: Datadog*
Set the following environment variables:
• `METRIC_CLIENT=datadog`
• `DD_AGENT_HOST` – The Datadog agent host IP.
• `DD_AGENT_PORT` – The Datadog agent port.
[<https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#monitoring|Configuring Airbyte - Monitoring>]
-------------------------
> *Note:* The OpenTelemetry metrics monitoring feature (via `values.yaml` configuration) is available *only for Self-Managed Enterprise*. For standard OSS deployments, use the environment variable approach described above. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.

<@U04S8PLJWMT> we are using 2.0 oss, is it an enterprise feature now?

Based on the knowledge sources for Airbyte 2.0, yes — *OpenTelemetry (OTel) metrics monitoring is an enterprise-only feature*, even in version 2.0. The documentation explicitly marks it as available only for *Self-Managed Enterprise* and not available for Core, Standard, Plus, Pro, or Enterprise Flex tiers. [<https://docs.airbyte.com/platform/2.0/operator-guides/open-telemetry|OpenTelemetry - 2.0>]
The `values.yaml` configuration also requires `edition: enterprise` to be set:
```global:
    edition: enterprise # This is an enterprise-only feature
    metrics:
        enabled: true
        otlp:
            enabled: true
            collectorEndpoint: "YOUR_ENDPOINT"
```
[<https://docs.airbyte.com/platform/2.0/operator-guides/collecting-metrics|Collecting Metrics - 2.0>]
For Airbyte OSS (non-enterprise), the environment variable approach (`PUBLISH_METRICS`, `METRIC_CLIENT`, `OTEL_COLLECTOR_ENDPOINT`) is still listed in the configuration reference [<https://docs.airbyte.com/platform/2.0/operator-guides/configuring-airbyte#monitoring|Configuring Airbyte 2.0>], but the knowledge sources do not explicitly confirm whether this still works end-to-end for OSS in 2.0. Given that a GitHub issue confirmed both Datadog and OTel monitoring became enterprise features starting with version 1.5, it's likely that full metrics monitoring requires an enterprise license in 2.0 as well.
If metrics monitoring is important to you, you may want to reach out to Airbyte directly or consider upgrading to Self-Managed Enterprise. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.