---
title: Monitor Docker
description: Use the Docker Monitoring template to monitor your Docker containers.
url: https://docs.influxdata.com/influxdb/v2/monitor-alert/templates/infrastructure/docker/
estimated_tokens: 893
product: InfluxDB OSS v2
version: v2
publisher: InfluxData
canonical: https://docs.influxdata.com/influxdb/v2/monitor-alert/templates/infrastructure/docker/
date: '2025-04-02T15:54:32-06:00'
lastmod: '2025-04-02T15:54:32-06:00'
---

This page documents an earlier version of InfluxDB OSS.[InfluxDB 3 Core](/influxdb3/core/) is the latest stable version.

#### API token hashing is enabled by default in InfluxDB OSS 2.9.0

Stronger token security: tokens are stored as hashes on disk, so a
copy of the database file doesn’t expose usable tokens. Existing
tokens are hashed on first startup and the original strings can’t
be recovered afterward — **capture any plaintext tokens you still
need before you upgrade**.

For more information, see [Token hashing](/influxdb/v2/admin/tokens/#token-hashing).

Use the [Docker Monitoring template](https://github.com/influxdata/community-templates/tree/master/docker) to monitor your Docker containers. First, [apply the template](#apply-the-template), and then [view incoming data](#view-incoming-data).
This template uses the [Docker input plugin](/telegraf/v1/plugins//#docker) to collect metrics stored in InfluxDB and display these metrics in a dashboard.

The Docker Monitoring template includes the following:

* one [dashboard](/influxdb/v2/reference/glossary/#dashboard): **Docker**
* one [bucket](/influxdb/v2/reference/glossary/#bucket): `docker, 7d retention`
* labels: Docker input plugin labels
* one [Telegraf configuration](/influxdb/v2/tools/telegraf-configs/): Docker input plugin
* one variable: `bucket`
* four [checks](/influxdb/v2/reference/glossary/#check): `Container cpu`, `mem`, `disk`, `non-zero exit`
* one [notification endpoint](/influxdb/v2/reference/glossary/#notification-endpoint): `Http Post`
* one [notification rule](/influxdb/v2/reference/glossary/#notification-rule): `Crit Alert`

For more information about how checks, notification endpoints, and notifications rules work together, see [monitor data and send alerts](/influxdb/v2/monitor-alert/).

## Apply the template

1. Use the [`influx` CLI](/influxdb/v2/reference/cli/influx/) to run the following command:

   ```
   influx apply -f https://raw.githubusercontent.com/influxdata/community-templates/master/docker/docker.yml
   ```

   For more information, see [influx apply](/influxdb/v2/reference/cli/influx/apply/).

   > [!Note]
> Ensure your `influx` CLI is configured with your account credentials and that configuration is active. For more information, see [influx config](/influxdb/v2/reference/cli/influx/config/).

2. [Install Telegraf](/telegraf/v1/introduction/installation/) on a server with network access to both the Docker containers and [InfluxDB v2 API](/influxdb/v2/reference/api/).

3. In your [Telegraf configuration file (`telegraf.conf`)](/influxdb/v2/tools/telegraf-configs/), do the following:

   * Depending on how you run Docker, you may need to customize the [Docker input plugin](/telegraf/v1/plugins//#docker) configuration, for example, you may need to specify the `endpoint` value.
   * Set the following environment variables:
     * INFLUX\_TOKEN: Token must have permissions to read Telegraf configurations and write data to the `telegraf` bucket. See how to [view tokens](/influxdb/v2/admin/tokens/view-tokens/).
     * INFLUX\_ORG: Name of your organization. See how to [view your organization](/influxdb/v2/admin/organizations/view-orgs/).
     * INFLUX\_HOST: Your InfluxDB host URL, for example, localhost, a remote instance, or InfluxDB Cloud.

4. [Start Telegraf](/influxdb/v2/write-data/no-code/use-telegraf/auto-config/#start-telegraf).

## View incoming data

1. In the InfluxDB user interface (UI), select **Dashboards** in the left navigation.

   Dashboards

2. Open the **Docker** dashboard to start monitoring.