@kapa.ai I have deployed OSS version on EKS. I need to ingest the metrics for monitoring in datadog. Is it feasible ? If yes, share the steps

It is feasible, but not via a direct “Airbyte → Datadog” integration for OSS on EKS. The current, documented path is: 1. Use OpenTelemetry metrics from Airbyte Enterprise (Self‑Managed) → Datadog Airbyte can emit metrics via OpenTelemetry OTLP HTTP to an OpenTelemetry Collector, and from there you can forward to Datadog. This is explicitly documented as a Self‑Managed Enterprise feature, not OSS. [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)] - You must be running the Enterprise edition (

global.edition: enterprise

) for this to work; the docs mark it as “Available Self‑Managed Enterprise” and “Not available” for other editions. [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)] - If you are on pure OSS (non‑Enterprise), the knowledge sources do not confirm that this OpenTelemetry configuration is available. 2. **If you do have Self‑Managed Enterprise on EKS, the high‑level steps are:** a. Deploy an OpenTelemetry Collector in your cluster - Configure it to accept OTLP over HTTP, e.g.: [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)]

yaml      receivers:        otlp:          protocols:            http:              endpoint: 0.0.0.0:4318

- In that Collector, add an exporter to Datadog (this part is in Datadog’s own docs; the Airbyte docs just point you to Datadog’s “Collector and Exporter” guide). [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)] b. Configure Airbyte to send metrics to that Collector In your Airbyte Helm

values.yaml

(Enterprise only): [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)]

yaml    global:      edition: enterprise  # Enterprise-only feature      metrics:        enabled: true        otlp:          enabled: true          # Must point to the OTLP HTTP metrics ingestion endpoint, e.g.:          # <http://otel-collector.default.svc.cluster.local:4318/v1/metrics>          collectorEndpoint: "YOUR_ENDPOINT"

c. Redeploy Airbyte - Apply the updated Helm values so the platform starts sending metrics to the Collector. [[OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)] From there, Datadog will receive Airbyte metrics via the Collector. [[Monitoring Airbyte](https://docs.airbyte.com/platform/operator-guides/collecting-metrics)] 3. Legacy Datadog integration (Docker‑only, not EKS) The docs state that the built‑in Datadog integration “only works on legacy Docker deployments of Airbyte” and that an improved version for Kubernetes is still in progress. [[Monitoring Airbyte](https://docs.airbyte.com/platform/operator-guides/collecting-metrics)] So for EKS you should not rely on the legacy `DD_AGENT_HOST`/`DD_AGENT_PORT` path as a supported solution. 4. Summary for your case (OSS on EKS) - The knowledge sources do not document a fully supported, direct Datadog integration for OSS on EKS. - The supported documented path to Datadog is: Self‑Managed Enterprise → OpenTelemetry → Collector → Datadog. [[Monitoring Airbyte](https://docs.airbyte.com/platform/operator-guides/collecting-metrics); [OpenTelemetry metrics](https://docs.airbyte.com/platform/operator-guides/open-telemetry)] - If you are strictly on OSS (non‑Enterprise), the docs do not confirm that you can enable the OpenTelemetry metrics feature, so I cannot reliably provide OSS‑specific steps beyond what’s above.

For pure OSS deployment, how can we ingest in datadog