Add instructions for Containerized Agent #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was recently trying to deploy this plugin into an API environment and was not receiving metrics in Datadog.
I have a multi-container deployment set up with docker-compose, and I was trying to send metrics from my application container (where uWSGI is running) to my dd-agent which is in a separate container (same docker network). I followed the instructions and didn't see any worrisome logs from uWSGI or the agent, but still nothing was coming through.
Eventually I noticed that dogstatsd was listening on
127.0.0.1:8125
in the dd-agent container, and noticed the documentation here mentioning "non-local" traffic. After configuring dogstatsd to listen for "non-local" traffic, dogstatsd was listening correctly to outside traffic and metrics began coming in. Yay!I thought it might be helpful to include a small note in the usage instructions here so that anyone attempting something similar in the future might save some troubleshooting time. Happy to take feedback or amend what I've added.