Estimated reading time: 8 minutes

Telegraf is an agent for collecting metrics and writing them to InfluxDB or other outputs.

GitHub repo:

Library reference

This content is imported from the official Docker Library docs, and is provided by the original uploader. You can view the Docker Hub page for this image at

Supported tags and respective Dockerfile links

Quick reference


Telegraf is an open source agent written in Go for collecting metrics and data on the system it’s running on or from other services. Telegraf writes data it collects to InfluxDB in the correct format.

Telegraf Official Docs


Using this image

Exposed Ports

  • 8125 StatsD
  • 8092 UDP
  • 8094 TCP

Using the default configuration

The default configuration requires a running InfluxDB instance as an output plugin. Ensure that InfluxDB is running on port 8086 before starting the Telegraf container.

Minimal example to start an InfluxDB container:

$ docker run -d --name influxdb -p 8083:8083 -p 8086:8086 influxdb

Starting Telegraf using the default config, which connects to InfluxDB at http://localhost:8086/:

$ docker run --net=container:influxdb telegraf

Using a custom config file

First, generate a sample configuration and save it as telegraf.conf on the host:

$ docker run --rm telegraf telegraf config > telegraf.conf

Once you’ve customized telegraf.conf, you can run the Telegraf container with it mounted in the expected location:

$ docker run -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro telegraf

Modify $PWD to the directory where you want to store the configuration file.

Read more about the Telegraf configuration here.

Using the container with input plugins

These examples assume you are using a custom configuration file that takes advantage of Docker’s built-in service discovery capability. In order to do so, we’ll first create a new network:

$ docker network create influxdb

Next, we’ll start our InfluxDB container named influxdb:

$ docker run -d --name=influxdb \
      --net=influxdb \

The telegraf.conf configuration can now resolve the influxdb container by name:

	urls = ["http://influxdb:8086"]

Finally, we start our Telegraf container and verify functionality:

$ docker run -d --name=telegraf \
      --net=influxdb \
      -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro \
$ docker logs -f telegraf


Start an instance of aerospike:

$ docker run -d --name aerospike \
      --net=influxdb \
      -p 3000-3003:3000-3003 \

Edit your Telegraf config file and set the correct connection parameter for Aerospike:

	servers = ["aerospike:3000"]

Restart your telegraf container to pick up the changes:

$ docker restart telegraf


Create an nginx_status.conf configuration file to expose metric data:

server {
    listen 8090;
    location /nginx_status {
        access_log off;

Start an Nginx container utilizing it:

$ docker run -d --name=nginx \
      --net=influxdb \
      -p 8090:8090 -p 8080:80 \
      -v $PWD/nginx_status.conf:/etc/nginx/conf.d/nginx_status.conf:ro \

Verify the status page: http://localhost:8090/nginx_status.

Configure the nginx input plugin in your Telegraf configuration file:

  urls = ["http://nginx:8090/nginx_status"]

Restart your telegraf container to pick up the changes:

$ docker restart telegraf


Telegraf has a StatsD plugin, allowing Telegraf to run as a StatsD server that metrics can be sent to. In order for this to work, you must first configure the StatsD plugin in your config file.

Run Telegraf with the UDP port 8125 exposed:

$ docker run -d --name=telegraf \
      --net=influxdb \
      -p 8125:8125/udp \
      -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro \

Send Mock StatsD data:

$ for i in {1..50}; do echo $i;echo "foo:1|c" | nc -u -w0 8125; done

Check that the measurement foo is added in the DB.

Supported Plugins Reference

Monitoring the host filesystem

One of the more common use cases for Telegraf is running it in a container to monitor the host filesystem using the inputs that take information from the /proc filesystem. This section only applies to monitoring a Linux host.

To do this, you can mount the host’s /proc filesystem inside of the container and set the location of /proc to an alternate location by using the HOST_PROC environment variable to change the location of where /proc is located. As an example:

$ docker run -d --name=telegraf \
      --net=influxdb \
      -e HOST_PROC=/host/proc \
      -v /proc:/host/proc:ro \
      -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro \

Monitoring docker containers

To monitor other docker containers, you can use the docker plugin and mount the docker socket into the container. An example configuration is below:

  endpoint = "unix:///var/run/docker.sock"

Then you can start the telegraf container.

$ docker run -d --name=telegraf \
      --net=influxdb \
      -v /var/run/docker.sock:/var/run/docker.sock \
      -v $PWD/telegraf.conf:/etc/telegraf/telegraf.conf:ro \

Refer to the docker plugin documentation for more information.

Image Variants

The telegraf images come in many flavors, each designed for a specific use case.


This is the defacto image. If you are unsure about what your needs are, you probably want to use this one. It is designed to be used both as a throw away container (mount your source code and start the container to start your app), as well as the base to build other images off of.


This image is based on the popular Alpine Linux project, available in the alpine official image. Alpine Linux is much smaller than most distribution base images (~5MB), and thus leads to much slimmer images in general.

This variant is highly recommended when final image size being as small as possible is desired. The main caveat to note is that it does use musl libc instead of glibc and friends, so certain software might run into issues depending on the depth of their libc requirements. However, most software doesn’t have an issue with this, so this variant is usually a very safe choice. See this Hacker News comment thread for more discussion of the issues that might arise and some pro/con comparisons of using Alpine-based images.

To minimize image size, it’s uncommon for additional related tools (such as git or bash) to be included in Alpine-based images. Using this image as a base, add the things you need in your own Dockerfile (see the alpine image description for examples of how to install packages if you are unfamiliar).


View license information for the software contained in this image.

As with all Docker images, these likely also contain other software which may be under other licenses (such as Bash, etc from the base distribution, along with any direct or indirect dependencies of the primary software being contained).

Some additional license information which was able to be auto-detected might be found in the repo-info repository’s telegraf/ directory.

As for any pre-built image usage, it is the image user’s responsibility to ensure that any use of this image complies with any relevant licenses for all software contained within.

library, sample, telegraf