StatsD

Agent Check

Overview

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.

Setup

Installation

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.

Configuration

Host

Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.

1. Edit the statsd.d/conf.yaml in the conf.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

2. Restart the Agent to start sending StatsD metrics and service checks to Datadog.

Containerized

For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.

Validation

Run the Agent’s status subcommand and look for statsd under the Checks section.

Data Collected

Metrics

Events

The StatsD check does not include any events.

Service Checks

statsd.is_up:

Returns CRITICAL if the StatsD server does not respond to the Agent’s health status request, otherwise OK.

statsd.can_connect:

Returns CRITICAL if the Agent cannot collect metrics about StatsD, otherwise OK.

Troubleshooting

Need help? Contact Datadog support.

Further Reading

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.