Documentation

Monitor Kubernetes using the InfluxData 1.x Platform

Monitor Kubernetes

The TICK stack is an easy and performant way to monitor the services that make up a Kubernetes cluster, whether or not you’re running InfluxDB in a Kubernetes cluster or somewhere else.

Why use the InfluxData

kube-influxdb Kubernetes monitoring project

The kube-influxdb project is a set of Helm charts to make collection and visualization of Kubernetes metrics easy. It uses Telegraf, the metrics collection agent is used as the primary agent to collect metrics and events

Read the kube-influxdb Getting Started guide.

Collect Kubernetes metrics with Telegraf

The Telegraf metrics collection agent can collect many types of metrics in a Kubernetes cluster, like Docker container metrics and stats from kubelets. It can even scrape Prometheus metrics API endpoints. Telegraf is used in the kube-influxdb project to collect metrics.

Read about setting up a Kubernetes monitoring architecture using Telegraf

Prometheus remote read and write support

InfluxDB supports the Prometheus remote read and write API for clusters already using Prometheus for metrics collection, but need require a more flexible time series data store.

Read about the Prometheus remote read and write API support in InfluxDB


Was this page helpful?

Thank you for your feedback!


The future of Flux

Flux is going into maintenance mode. You can continue using it as you currently are without any changes to your code.

Flux is going into maintenance mode and will not be supported in InfluxDB 3.0. This was a decision based on the broad demand for SQL and the continued growth and adoption of InfluxQL. We are continuing to support Flux for users in 1.x and 2.x so you can continue using it with no changes to your code. If you are interested in transitioning to InfluxDB 3.0 and want to future-proof your code, we suggest using InfluxQL.

For information about the future of Flux, see the following: