You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the config option use_dogstatsd: false there are various aspects of the agent's status that make it look like something is broken. Some examples:
Status
When running status an error is shown:
====================
Dogstatsd (v 5.14.1)
====================
Dogstatsd is not running.
You can get more details in the logs:
<stderr>, /var/log/datadog/dogstatsd.log
It seems like this could be avoided since the config knows that DogStatsD is intentionally disabled.
Supervisor
I can't repro atm, but I've seen the following error when starting / restarting / etc the agent:
datadog-agent:dogstatsd FATAL Exited too quickly (process log may have details)
This is likely because dogstatsd is bailing and supervisor isn't aware it shouldn't start. Again, predicating the need to start on the config option would be helpful!
Motivation
We don't use DogStatsD internally. We realize this is likely not the common case. Unfortunately if our teammates try and manipulate the agent these errors end up being a false positive, as they aren't errors at all for us!
The text was updated successfully, but these errors were encountered:
Summary
When using the config option
use_dogstatsd: false
there are various aspects of the agent's status that make it look like something is broken. Some examples:Status
When running
status
an error is shown:It seems like this could be avoided since the config knows that DogStatsD is intentionally disabled.
Supervisor
I can't repro atm, but I've seen the following error when starting / restarting / etc the agent:
This is likely because dogstatsd is bailing and supervisor isn't aware it shouldn't start. Again, predicating the need to start on the config option would be helpful!
Motivation
We don't use DogStatsD internally. We realize this is likely not the common case. Unfortunately if our teammates try and manipulate the agent these errors end up being a false positive, as they aren't errors at all for us!
The text was updated successfully, but these errors were encountered: