Self-host Chronograf with Levelrail

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.

  • Authorinfluxdata
  • LicenceMIT
  • Memory256 MiB
  • Services1

How to self-host Chronograf

  1. Pull the images

    One image is pulled on your server.

    Show images
    • chronograf:1.11.6
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 8888.

  3. Fill in the secrets

    1 setting is preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Open the page and enter the address of your InfluxDB server to connect it.

Chronograf requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
8888
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
MIT, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Chronograf. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Chronograf docs page.

Deploy Chronograf your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Chronograf from the CLI

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

Deploy Chronograf with the API

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

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

Chronograf configuration

Chronograf services

ServiceImagePortsVolumes
chronograf chronograf:1.11.6 8888 data -> /var/lib/chronograf

Chronograf environment variables

VariableServiceValue
BOLT_PATH chronograf Preset by the template

Ports and volumes

Ports
8888
Volumes
1 named mount: data -> /var/lib/chronograf

Chronograf FAQ

How much memory does Chronograf need?

The catalog lists about 256 MiB of memory for Chronograf.

Does Chronograf run on arm64?

For Chronograf, arm64 support is not confirmed; amd64 is unknown.

What licence is Chronograf under?

Chronograf is licensed under MIT, which is permissive, with few conditions on reuse.

Does Chronograf need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Chronograf use?

Chronograf listens on port 8888 inside the stack.

Where does Chronograf keep its data?

In a named volume: data mounted at /var/lib/chronograf.

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.

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