Self-host Telegraf with Levelrail

Plugin driven agent that collects metrics and exposes them for Prometheus. The install form carries telegraf.conf as an editable file, so it starts with CPU, memory and disk inputs already wired.

  • Authorinfluxdata
  • LicenceMIT
  • Memory128 MiB
  • Services1

How to self-host Telegraf

  1. Pull the images

    One image is pulled on your server.

    Show images
    • telegraf:1.40.3
  2. Create the app

    One service starts in a single Compose app, on port 9273.

  3. Fill in the secrets

    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

  • Scrape port 9273 from Prometheus or open the address to see the raw metrics, then edit the config file setting to add inputs and outputs.

Telegraf requirements

Memory
About 128 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
9273
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 Telegraf. 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 Telegraf docs page.

Deploy Telegraf your way

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

Deploy Telegraf from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain telegraf=app.example.com.

levelrail-cli templates install telegraf --name my-telegraf

Deploy Telegraf with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/telegraf/install \
  -d '{
    "name": "my-telegraf"
  }'

Telegraf configuration

Telegraf services

ServiceImagePortsVolumes
telegraf telegraf:1.40.3 9273 none

Telegraf environment variables

The catalog lists no environment variables for this template.

Ports and volumes

Ports
9273
Volumes
none

Telegraf FAQ

How much memory does Telegraf need?

The catalog lists about 128 MiB of memory for Telegraf.

Does Telegraf run on arm64?

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

What licence is Telegraf under?

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

Does Telegraf need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Telegraf use?

Telegraf listens on port 9273 inside the stack.

Can I deploy Telegraf 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 Telegraf, 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 telegraf:1.40.3 is what you deploy there.

levelrail-cli templates install telegraf --name my-telegraf