# Self-host Chronograf

> A web interface to explore, graph and alert on time series stored in InfluxDB. Add your InfluxDB connection from the first screen; it has no login of its own, so restrict who can reach it.

- Page: https://levelrail.com/templates/chronograf/
- JSON: https://levelrail.com/templates/chronograf.json
- Category: Monitoring
- Licence: MIT (Permissive license)
- Source: https://github.com/influxdata/chronograf
- Upstream docs: https://docs.influxdata.com/chronograf/

## Requirements
- Memory: about 256 MiB
- amd64: unknown, arm64: unknown
- Needs configuration before start: no
- Pinned image tag: 1.11.6

## Services

| Service | Image | Tag | Ports | Volumes |
| --- | --- | --- | --- | --- |
| chronograf | chronograf | 1.11.6 | 8888 | data -> /var/lib/chronograf |

## Environment

| Service | Variable | Kind |
| --- | --- | --- |
| chronograf | BOLT_PATH | preset |

## Deploy

### CLI

```bash
levelrail-cli templates deploy chronograf --name my-chronograf
```

### API

```bash
curl -X POST -H "Authorization: Bearer $TOKEN" \
  https://levelrail.example.com/api/v1/service-templates/chronograf/deploy
```

Create a token in the dashboard first. This one-click route deploys it as a trial app you can keep or remove.

## First run
1. Open the page and enter the address of your InfluxDB server to connect it.

## Questions

### Can I deploy Chronograf on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Chronograf, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image chronograf:1.11.6 is what you deploy there.

Self-host Chronograf, Chronograf docker compose file, deploy Chronograf on a VPS: this page lists the pinned image, ports, volumes and the commands for each.
