---
title: Administer Telegraf Controller
description: 'Manage a Telegraf Controller server: manage and troubleshoot the database, monitor server health, configure networking, and run Telegraf Controller as a system service.'
url: https://docs.influxdata.com/telegraf/controller/admin/
estimated_tokens: 711
publisher: InfluxData
canonical: https://docs.influxdata.com/telegraf/controller/admin/
date: '2026-09-22T08:51:42-06:00'
lastmod: '2026-09-22T08:51:42-06:00'
---

Administer and operate a Telegraf Controller server.
This section covers operator-level tasks: managing the database that stores
Telegraf Controller data, monitoring server health, and configuring the
server’s runtime environment.

## [Manage the database](/telegraf/controller/admin/database/)

Telegraf Controller stores all application state in a SQLite (default) or PostgreSQL database. Learn where the database lives, how to configure it, and how to back it up and restore it.

## [Secure Telegraf Controller with TLS](/telegraf/controller/admin/secure-tls/)

Serve Telegraf Controller over HTTPS and configure Telegraf agents to trust the certificate so agents can fetch configurations and send heartbeats over encrypted connections.

## [High availability](/telegraf/controller/admin/high-availability/)

Run multiple Telegraf Controller nodes against a shared PostgreSQL-compatible database for continuous availability. One node is elected leader to run cluster-wide background work while every node serves traffic, and a standby takes over if the leader fails.

## [Monitor](/telegraf/controller/admin/monitor/)

Monitor the health of a Telegraf Controller server using its unauthenticated health endpoints and its log output.

## [Networking and ports](/telegraf/controller/admin/networking/)

When you run Telegraf Controller, identify the ports and listeners it uses, determine which clients need access to each one, and expose them safely with Transport Layer Security (TLS), firewalls, and reverse proxies.

## [Run as a service](/telegraf/controller/admin/run-as-a-service/)

Run Telegraf Controller as a managed system service with systemd, a LaunchDaemon, or NSSM, so it starts on boot, restarts on failure, and shuts down cleanly.

## [Audit logs](/telegraf/controller/admin/audit-logs/)

Telegraf Controller records security-relevant events to a tamper-evident, append-only audit log. Use audit logs to investigate access, detect unauthorized changes, and demonstrate compliance.

## [Troubleshoot Telegraf Controller](/telegraf/controller/admin/troubleshoot/)

Find the fix for a Telegraf Controller problem by symptom: startup failures, port conflicts, rejected agent heartbeats, TLS errors, and database errors.

## Other administration tasks

Additional operator documentation lives in the following sections:

* [Install Telegraf Controller](/telegraf/controller/install/):
  download, install, and set up the server and its database.
* [Upgrade](/telegraf/controller/install/upgrade/):
  upgrade to a new version of Telegraf Controller.
* [Authentication](/telegraf/controller/authentication/):
  configure local, LDAP, or OIDC authentication.

#### Related

* [Telegraf Controller configuration options](/telegraf/controller/reference/config-options/)
* [Install Telegraf Controller](/telegraf/controller/install/)