Skip to content

Commit

Permalink
Remove Datadog autodiscovery on Render
Browse files Browse the repository at this point in the history
  • Loading branch information
anurag committed May 12, 2021
1 parent be6d81e commit 3bb9abb
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
6 changes: 4 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
FROM datadog/agent:7

# disable all Kubernetes checks (they don't work on Render)
RUN rm -rf /etc/datadog-agent/conf.d/kube*
# disable autoconfigured checks; DD container checks
# do not work as-is on Render since there's no access
# to Kubelet/kube-state-metrics.
ENV DD_AUTOCONFIG_FROM_ENVIRONMENT=false

ENV NON_LOCAL_TRAFFIC=true
ENV DD_LOGS_STDOUT=yes
Expand Down
2 changes: 0 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,5 +9,3 @@ This example deploys Datadog's [Docker agent](https://docs.datadoghq.com/agent/d
The URL will look like `datadog-agent-lkyz` with APM available on TCP port `8126` and DogStatsD on UDP port `8125`.

> You will need to configure your Datadog API key by setting the `DD_API_KEY` environment variable to your private service.
Errors of the form `"Unable to detect the kubelet URL automatically: impossible to reach Kubelet with host:` can be safely ignored. The kubelet is part of the Render control plane and inaccessible to user workloads. The DataDog Agent will still be able to capture and send metrics from your applications.

0 comments on commit 3bb9abb

Please sign in to comment.