Hi again!
Have a dockerized datadog agent will make it reachable by the worker without extra network configuration (like using
network_mode: "host"
on the worker)
You were absolutely right, I had to setup the network_mode as host, otherwise it did not work
So now I’ve dockerised the agent with this configuration:
datadog:
image: gcr.io/datadoghq/agent:7
container_name: dd-agent
environment:
- DD_API_KEY=${DD_API_KEY}
- DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /proc/:/host/proc/:ro
- /sys/fs/cgroup:/host/sys/fs/cgroup:ro
airbyte-metrics:
image: airbyte/metrics-reporter:${VERSION}
container_name: airbyte-metrics
environment:
- PUBLISH_METRICS=true
- DD_AGENT_HOST=dd-agent
- DD_DOGSTATSD_PORT=8125
- DATABASE_USER=${DATABASE_USER}
- DATABASE_URL=${DATABASE_URL}
- DATABASE_PASSWORD=${DATABASE_PASSWORD}
and it works perfectly for airbyte-metrics-reporter
(I’m able to see the metrics in my DD dashboards, under metrics_reporter.name_of_metric
). However, adding the three env var to the worker
container:
worker:
image: airbyte/worker:${VERSION}
logging: *default-logging
container_name: airbyte-worker
restart: unless-stopped
environment:
- AIRBYTE_VERSION=${VERSION}
- AUTO_DISABLE_FAILING_CONNECTIONS=${AUTO_DISABLE_FAILING_CONNECTIONS}
- etc.
- PUBLISH_METRICS=true
- DD_AGENT_HOST=dd-agent
- DD_DOGSTATSD_PORT=8125
Does not seem to trigger any monitoring for worker on my side… Am I missing something?
I’ve also tried to add the following to the datadog container, with no results either:
datadog:
image: gcr.io/datadoghq/agent:7
container_name: dd-agent
environment:
- DD_API_KEY=${DD_API_KEY}
- DD_DOGSTATSD_NON_LOCAL_TRAFFIC=true
- DD_LOGS_ENABLED=true
- DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true
- DD_SITE=datadoghq.com
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /proc/:/host/proc/:ro
- /sys/fs/cgroup:/host/sys/fs/cgroup:ro
- /var/lib/docker/containers:/var/lib/docker/containers:ro
Note: I’m on v0.38.4-alpha version
Thanks again for your help!