Issues with Datadog Integration in Airbyte Deployment

Summary

User is experiencing issues with Datadog integration in their Airbyte deployment using ArgoCD and Helm. They are seeing some metrics but not job-specific ones, and are using GCS instead of MinIO, which may require additional configurations. The warning indicates missing stats for a specific job.


Question

Hi guys, we’re trying to get the datadog integration working on our airbyte deployment. We’re currently using argocd to deploy so it’s doing a helm template before applying which has led to some issues. We’re seing some metrcis, but not job specific ones. We’re using gcs instead of minio so i’m not sure if there’s additonal configs

2024-11-14 21:39:52 WARN i.a.c.s.h.h.StatsAggregationHelper(hydrateWithStats):150 - Missing stats for job 2187 attempt 0

Also we’re on the 1.1.0 version of the helm chart.

Any help or pointing in the right direction would be awesome



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['datadog-integration', 'airbyte-deployment', 'argocd', 'helm', 'gcs', 'metrics', 'missing-stats']

We’re also noticing that the metrics-server is giving out these warning errors, but i’m not sure what it’d be hoping to find at localhost

2024-11-14 23:09:19 WARN i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [8722bf60, L:/127.0.0.1:47731 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused

<@U081F8QD6BS> did you find a solution to this problem?

<@U07DH2PNA11> not yet, still seeing this error even after setting our metrics to be datadog. I reached out and created this issue on github. Since I think the major issue might be on the server

https://github.com/airbytehq/airbyte/issues/48503#issuecomment-2483989283

We’re also noticing that the metrics-server is giving out these warning errors, but i’m not sure what it’d be hoping to find at localhost

2024-11-14 23:09:19 WARN i.m.s.r.u.Loggers$Slf4JLogger(warn):299 - [8722bf60, L:/127.0.0.1:47731 - R:localhost/127.0.0.1:8125] An exception has been observed post termination, use DEBUG level to see the full stack: java.net.PortUnreachableException: recvAddress(..) failed: Connection refused

<@U081F8QD6BS> did you find a solution to this problem?

<@U07DH2PNA11> not yet, still seeing this error even after setting our metrics to be datadog. I reached out and created this issue on github. Since I think the major issue might be on the server

https://github.com/airbytehq/airbyte/issues/48503#issuecomment-2483989283