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 included in the Datadog Agent package, so you don't need to install anything else on any servers that run StatsD.
To configure this check for an Agent running on a host:
-
Edit the
statsd.d/conf.yaml
in theconf.d/
folder at the root of your Agent's configuration directory. See the sample statsd.d/conf.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.
For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
Parameter | Value |
---|---|
<INTEGRATION_NAME> |
statsd |
<INIT_CONFIG> |
blank or {} |
<INSTANCE_CONFIG> |
{"host": "%%host%%", "port":"8126"} |
-
Collecting logs is disabled by default in the Datadog Agent, you need to enable it in
datadog.yaml
:logs_enabled: true
-
Add this configuration block to your
statsd.d/conf.yaml
file to start collecting your Supervisord Logs:logs: - type: file path: /path/to/my/directory/file.log source: statsd
Change the
path
parameter value and configure it for your environment. See the sample statsd.d/conf.yaml for all available configuration options.
Run the Agent's status subcommand and look for statsd
under the Checks section.
See metadata.csv for a list of metrics provided by this integration.
The StatsD check does not include any events.
See service_checks.json for a list of service checks provided by this integration.
Need help? Contact Datadog support.
Additional helpful documentation, links, and articles: