--- title: Telegraf Enterprise & Controller 1.2: Know Your Fleet's... description: Telegraf Controller 1.2 adds tools for managing a fleet of Telegraf agents, including security advisory scanning in Telegraf Enterprise. It matches published... canonical: https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Telegraf Enterprise & Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health | daily.dev og:description: Telegraf Controller 1.2 adds tools for managing a fleet of Telegraf agents, including security advisory scanning in Telegraf Enterprise. It matches published... og:url: https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0 og:image: https://api.daily.dev/og/posts/nuk7J5Tc0.png og:image:alt: Telegraf Enterprise & Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Telegraf Enterprise & Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health **[InfluxData](https://daily.dev/sources/influxdb)** · 5 min read · 0 upvotes · 0 comments ## Summary Telegraf Controller 1.2 adds tools for managing a fleet of Telegraf agents, including security advisory scanning in Telegraf Enterprise. It matches published advisories against each agent's reported version to show exactly which agents need updates. Every Controller user, free or Enterprise, gets agent-level metrics, errors, and logs, fleet summary visualizations, and a heartbeat service health indicator with a new GET /api/heartbeat/health endpoint. Telegraf Controller now ships as an official Docker image, influxdata/telegraf-controller, runnable with a single docker run command exposing ports 8888 and 8000. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I run Telegraf Controller in Docker? Run a docker container from the official influxdata/telegraf-controller image, publishing port 8888 for the web and API and port 8000 for the heartbeat endpoint that agents connect to. Set the TELEGRAF_CONTROLLER_EULA=accept environment variable and mount a volume at /var/lib/telegraf-controller so data survives restarts and upgrades. Then open localhost:8888 to create the owner account. _Teams rolling out fleet monitoring tools track setup changes like this via daily.dev._ ### How does Telegraf Enterprise know which agents are vulnerable to a security advisory? Telegraf Controller compares each published advisory's affected version ranges against the Telegraf version every agent reports in its heartbeat. A Security page shows fleet-wide exposure by severity, and the Agents page gets an Advisories column and exposure filter so a reviewer gets a filtered list of affected agents and versions instead of a manual audit. Air-gapped deployments can import a signed advisory file manually. _Security reviewers tracking fleet exposure can follow advisory tooling updates like this on daily.dev._ ### How do I enable per-agent logs and statistics in Telegraf heartbeat data? Add 'statistics' and 'logs' to the heartbeat plugin's include list. This lets each heartbeat carry runtime statistics and a sample of recent Telegraf logs, visible on the agent detail page as error, warning, and metric counts charted across the last 24 heartbeats, plus log entries from the latest heartbeat. _Ops teams debugging silent agent failures can keep up with monitoring features like this on daily.dev._ ## Similar posts on daily.dev - [Telegraf Enterprise Now Generally Available: Manage Telegraf Fleets at Scale](https://daily.dev/posts/telegraf-enterprise-now-generally-available-manage-telegraf-fleets-at-scale-muvnraaa0) · InfluxData · 0 upvotes · 0 comments - [Telegraf Enterprise Beta is Now Available: Centralized Control for Telegraf at Scale](https://daily.dev/posts/telegraf-enterprise-beta-is-now-available-centralized-control-for-telegraf-at-scale-5ypawebzy) · InfluxData · 0 upvotes · 0 comments - [Telegraf Controller 1.1: Make Fleet-Wide Config Changes with a Single Edit](https://daily.dev/posts/telegraf-controller-1-1-make-fleet-wide-config-changes-with-a-single-edit-57wf9klm8) · InfluxData · 0 upvotes · 0 comments - [End-to-end observability at scale starts with knowing what you’re running](https://daily.dev/posts/end-to-end-observability-at-scale-starts-with-knowing-what-you-re-running-cyjxz0asb) · Dynatrace · 0 upvotes · 0 comments - [Manage your OpenTelemetry Collectors with Fleet Management in Grafana Cloud](https://daily.dev/posts/manage-your-opentelemetry-collectors-with-fleet-management-in-grafana-cloud-livckhr5u) · Grafana Labs · 0 upvotes · 0 comments --- Tags: [#docker](https://daily.dev/tags/docker), [#observability](https://daily.dev/tags/observability) [View this post on daily.dev](https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Telegraf Enterprise \u0026 Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health","url":"https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0"},"datePublished":"2026-10-27T14:28:13.903Z","dateModified":"2026-10-27T14:28:46.072Z","description":"Telegraf Controller 1.2 adds tools for managing a fleet of Telegraf agents, including security advisory scanning in Telegraf Enterprise. It matches published...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a15749ba39c3a8a86b53995a15973827?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/a15749ba39c3a8a86b53995a15973827?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"InfluxData","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"InfluxData","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/fe5458bda4564e9eb0e51001b4b81374","url":"https://daily.dev/sources/influxdb"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"docker,observability","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"InfluxData","item":"https://daily.dev/sources/influxdb"},{"@type":"ListItem","position":3,"name":"Telegraf Enterprise \u0026 Controller 1.2: Know Your Fleet's Security Exposure, Versions, and Health"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/telegraf-enterprise-controller-1-2-know-your-fleet-s-security-exposure-versions-and-health-nuk7j5tc0#faq","mainEntity":[{"@type":"Question","name":"How do I run Telegraf Controller in Docker?","acceptedAnswer":{"@type":"Answer","text":"Run a docker container from the official influxdata/telegraf-controller image, publishing port 8888 for the web and API and port 8000 for the heartbeat endpoint that agents connect to. Set the TELEGRAF_CONTROLLER_EULA=accept environment variable and mount a volume at /var/lib/telegraf-controller so data survives restarts and upgrades. Then open localhost:8888 to create the owner account. Teams rolling out fleet monitoring tools track setup changes like this via daily.dev."}},{"@type":"Question","name":"How does Telegraf Enterprise know which agents are vulnerable to a security advisory?","acceptedAnswer":{"@type":"Answer","text":"Telegraf Controller compares each published advisory's affected version ranges against the Telegraf version every agent reports in its heartbeat. A Security page shows fleet-wide exposure by severity, and the Agents page gets an Advisories column and exposure filter so a reviewer gets a filtered list of affected agents and versions instead of a manual audit. Air-gapped deployments can import a signed advisory file manually. Security reviewers tracking fleet exposure can follow advisory tooling updates like this on daily.dev."}},{"@type":"Question","name":"How do I enable per-agent logs and statistics in Telegraf heartbeat data?","acceptedAnswer":{"@type":"Answer","text":"Add 'statistics' and 'logs' to the heartbeat plugin's include list. This lets each heartbeat carry runtime statistics and a sample of recent Telegraf logs, visible on the agent detail page as error, warning, and metric counts charted across the last 24 heartbeats, plus log entries from the latest heartbeat. Ops teams debugging silent agent failures can keep up with monitoring features like this on daily.dev."}}]} ```