a spring-boot-starter for pushing metrics to a dogstatsd-agent.
Switch branches/tags
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
src Feature: extended colon handling (#3) Nov 6, 2018
.gitignore development draft Jan 5, 2018
.travis.yml added tests and docs Jan 12, 2018
LICENSE Initial commit Jan 5, 2018
README.md monkey task Nov 6, 2018
pom.xml updating poms for branch'release/1.0.3' with non-snapshot versions Nov 6, 2018



MIT License Maven metadata URI Build Status

this project will easily push your metrics to a dogstatsd-agent in a spring-boot environment. For now, this project will only support Spring-Boot 1.5.x, since in 2.0.x, spring will introduce Micrometer as an abstraction for pushing metrics to various vendors.


Add dogstatsd-spring-boot-starter as dependency.

If you use Maven, add the starter to your dependencies:


If you use Gradle, add your dependency as follows:

repositories {

dependencies {
    compile 'com.github.robertnetz:dogstatsd-spring-boot-starter:1.0.3'


As soon as the starter was added to your project, it will send your actuator metrics to your dogstatsd-agent. by default it will send to localhost:8125.

you can update the configuration by adding new keys to your application.yml as follows.

  host: otherhost.example.com
  port: 12345

a feature of the dogstatsd is the tagging-support. to tag all your metrics statically with a provided set of tags, you have to specify them like this:

    - foo
    - bar
    - bam
    - baz

if you like to have a static prefix to all your metrics, you can do it like that:

  prefix: superapp

you also can disable the metrics export by configuration:

  enabled: false

You might not want to export spring actuators' SystemPublicMetrics, then you'll have to disable them explicitly by:

  includeActuatorMetrics: false

Metric name sanitization

Some libraries you use might be recording metrics with : in their names. These are currently not supported by the java-dogstatsd-client and cause errors. There are a few strategies available:

  nameSanitizer: raise  # default

The default strategy is raise, and will raise an exception when a : character is encountered in a metric name. This will allow you to quickly fix any code under your control which reported these metrics.

Other available strategies are:

  • escape: replace any : with a -
  • ignore: silently skip reporting the metric with the illegal name