This check monitors the availability and uptime of non-Datadog StatsD servers. It also tracks the number of metrics, by metric type, received by StatsD.
This check does NOT forward application metrics from StatsD servers to Datadog. It collects metrics about StatsD itself.
The StatsD check is packaged with the Agent, so simply install the Agent on any servers that run StatsD.
Create a file
statsd.yaml in the Agent’s
conf.d directory. See the sample statsd.yaml for all available configuration options:
init_config: instances: - host: localhost port: 8126 # or wherever your statsd listens
Restart the Agent to start sending StatsD metrics and service checks to Datadog.
Run the Agent’s
status subcommand and look for
statsd under the Checks section:
Checks ====== [...] statsd ------- - instance #0 [OK] - Collected 3 metrics, 0 events & 2 service checks [...]
The statsd check is compatible with all major platforms.
|The number of counter metrics currently seen by StatsD
|The number of gauge metrics currently seen by StatsD
|The number of timer metrics currently seen by StatsD
The StatsD check does not include any event at this time.
Returns CRITICAL if the StatsD server does not respond to the Agent’s health status request, otherwise OK.
Returns CRITICAL if the Agent cannot collect metrics about StatsD, otherwise OK.
Need help? Contact Datadog Support.
If you don’t know what StatsD is and how does it work, check out our blog post about it
To get a better idea of how (or why) to visualize StatsD metrics with Counts Graphing with Datadog, check out our series of blog posts about it.