Yes, Airbyte supports two ways to collect metrics - using Datadog or Open Telemetry. For Datadog, you need to set two environment variables:

METRIC_CLIENT

to

datadog

and

PUBLISH_METRICS

to

true

. Additionally, you need to configure two more environment variables to the Datadog endpoint:

DD_AGENT_HOST

to the IP where the Datadog agent is running and

DD_DOGSTATSD_PORT

to the port the Datadog agent is using. You can find the complete list of metrics Airbyte is sending [here](https://github.com/airbytehq/airbyte-platform/blob/master/airbyte-metrics/metrics-lib/src/main/java/io/airbyte/metrics/lib/OssMetricsRegistry.java). For Open Telemetry, you need to change

METRIC_CLIENT

to

otel

in your

.env

file and configure

OTEL_COLLECTOR_ENDPOINT

to tell Airbyte where to send metrics RPC to. You can also run Airbyte and Open Telemetry locally or on Kubernetes. For local setup, you need to clone the repository from

opentelemetry-java-docs

and run it. Then, change

METRIC_CLIENT

to

otel

and

OTEL_COLLECTOR_ENDPOINT

to

<http://host.docker.internal:4317>

. For Kubernetes setup, you need to run open telemetry collector in the same Kubernetes context and edit

kube/overlays/stable/.env

to add

METRIC_CLIENT=otel

and

OTEL_COLLECTOR_ENDPOINT=<address>

. For more details, you can refer to the [Collecting Metrics](https://docs.airbyte.com/operator-guides/collecting-metrics) guide in the Airbyte documentation.