Zack Mattor
11/25/2025, 4:53 PMkapa.ai
11/25/2025, 4:53 PMPUBLISH_METRICS environment variable, which defaults to false. Additionally, the metrics client (METRIC_CLIENT) must be explicitly set to datadog for Datadog integration to be active. If these are not set, Airbyte should not attempt to send metrics to Datadog by default [Configuring Airbyte Monitoring](https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#monitoring). However, the warning you are seeing (WARN com.datadog.profiling.uploader.ProfileUploader - Failed to upload profile...) suggests that the Datadog Java profiler agent is present in the JVM and is attempting to send profiling data to a local Datadog agent, regardless of Airbyte’s own metrics configuration. The knowledge sources do not explicitly mention the Java profiler or how to disable it in the Helm charts. It is possible that the base Docker images used by Airbyte include the Datadog Java agent, which may be enabled by default at the JVM level, independent of Airbyte’s own metrics settings. What you can do: - Double-check your values.yaml and ensure that PUBLISH_METRICS is set to false and METRIC_CLIENT is not set to datadog. - If the warnings persist, it may be necessary to override or remove any JVM options that enable the Datadog profiler agent. This is not documented in the provided knowledge sources, so you may need to check your container or Helm chart customizations for any references to Datadog Java agent options. If you continue to see these warnings and you have confirmed that Airbyte’s metrics settings are disabled, it is likely due to the Java agent being present in the image. The knowledge sources do not provide a direct solution for disabling the Java profiler in this context, so you may need to consult the Airbyte community or inspect the Docker images for further troubleshooting. Summary: Datadog metrics are disabled by default in Helm V2 charts, but the Java profiler agent may still be active if present in the image. The knowledge sources do not provide explicit steps to disable the profiler, so further investigation into your deployment’s JVM options or Docker image may be required [Configuring Airbyte Monitoring](https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#monitoring).Zack Mattor
11/25/2025, 4:55 PMkapa.ai
11/25/2025, 4:56 PMkapa.ai
11/25/2025, 4:56 PMMICROMETER_METRICS_STATSD_FLAVOR, MICROMETER_METRICS_ENABLED, etc.) are related to Micrometer metrics, which is a metrics instrumentation library often used in Java applications. In the context of Airbyte, the official documentation and configuration references focus on the following variables for controlling metrics and Datadog integration: - PUBLISH_METRICS - METRIC_CLIENT (should be set to datadog or otel) - DD_AGENT_HOST - DD_AGENT_PORT - OTEL_COLLECTOR_ENDPOINT According to the documentation, metrics collection and Datadog integration are disabled by default unless you explicitly enable them by setting PUBLISH_METRICS to true and configuring the appropriate client [Configuring Airbyte Monitoring](https://docs.airbyte.com/platform/operator-guides/configuring-airbyte#monitoring). The knowledge sources do not mention the MICROMETER_METRICS_* variables as part of the standard Airbyte configuration for metrics or Datadog. Therefore, based on the documentation, these variables are not required to disable Datadog or metrics collection in Airbyte, and their presence does not override the main PUBLISH_METRICS and METRIC_CLIENT settings. Summary: - The official way to control metrics and Datadog integration in Airbyte is through PUBLISH_METRICS and METRIC_CLIENT. - The MICROMETER_METRICS_* variables are not documented in the Airbyte knowledge sources as being necessary for disabling metrics or Datadog integration. - If PUBLISH_METRICS is set to "false", metrics collection (including Datadog) should be disabled, regardless of the MICROMETER_METRICS_* values. If you are still seeing Datadog-related warnings, it is likely due to something outside the documented Airbyte configuration, such as a Java agent included in the Docker image, as previously mentioned. The knowledge sources do not provide further details on the MICROMETER_METRICS_* variables or their impact on Airbyte’s metrics behavior.