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.

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, to collect metrics and
events and includes a set of pre-configured Chronograf dashboards.

Prometheus remote read and write support

InfluxDB supports the Prometheus remote read and write API for clusters already
using Prometheus for metrics collection. See the
FAQ for more information on why a more flexible
time series data store is useful.

Frequently asked questions

How is the InfluxData Platform (TICK) different from Prometheus?

InfluxDB was purpose-built as a time series database. Overall, it is more
flexible and can handle more use cases than Prometheus alone, such as irregular
events and string data types.

Many InfluxDB users find it provides several advantages over Prometheus:
- Handles event data that comes in at irregular intervals, e.g. structured logs,
application events, and trace data.
- Works well as a centralized long-term metrics store for federated Prometheus
servers in multiple clusters.

Should I run InfluxDB in Kubernetes?

While Kubernetes is rapidly becoming a stable deployment platform for stateful
applications, it still introduces significant complexity and few benefits for
database workloads.

Therefore, we do not currently recommend running InfluxDB or InfluxDB
Enterprise on Kubernetes in production. While many users have managed to run the
databases in Kubernetes successfully, many InfluxDB users have also experienced
issues including significant downtime and even loss of data due to Kubernetes
rescheduling pods or problems with mounted volumes.