Kubernetes monitoring
Gain real-time visibility into your entire container-based environment to unify all your metrics and events for faster root cause analysis.
Find out how by reading the Kubernetes monitoring tech paper.
Why monitor Kubernetes?
Get broad insight and act in time
Monitor all Prometheus metrics, application events, K8s annotations, and logs from one pane.
Optimize to be competitive at lower cost
InfluxDB real-time stream analytics, highly efficient compression and compaction allow data to be ingested and stored cost-effectively.
HA and scalability
InfluxDB’s purpose-built design for time series allows for very high volume storage of monitoring records while providing horizontal scalability and high availability with clustering.InfluxData support for Kubernetes monitoring
- InfluxData’s open source, plugin-based agent Telegraf (200+ plugins) collects metrics and events, from Kubernetes nodes, pods, master node and all Prometheus/metric endpoints.
- In Kubernetes cluster environments, Telegraf can be deployed as a DaemonSet in every node, as an application sidecar in pods, or as a central collector.
- InfluxData has implemented a Kubernetes Operator to facilitate the deployment and management of InfluxDB Instances.
Put Kubernetes monitoring components & integrations to work for you
- Kubernetes monitoring Telegraf plugins — such as Telegraf Kubernetes input plugin, Telegraf plugin for service discovery of Prometheus /metrics, and Telegraf self-monitoring of metric pipeline plugins — facilitate monitoring Kubernetes.
- Community integrations such as prepackaged Kubernetes apps (which can be deployed to Google Kubernetes Engine in minutes) and the Telegraf InfluxDB and Grafana package (for metrics collection, storage, & visualization).
- Kubernetes-specific capabilities such as Helm Charts for Faster Node Deployment; Native Kubernetes Operators; High Availability (HA) and scalability of monitored data; and integration with Prometheus monitoring.
Featured customers:
“It’s a unique product that provides features like clustering, commercial support, and data retention that matter a lot to us. That’s why we picked InfluxData and that’s why several years ago, we rolled out our first integration with InfluxDB for the Kubernetes clusters that we deploy.”
“Before InfluxDB, we were like a lot of organizations where we didn’t have the visibility into what was going on in our K8s and Docker environments. Now with InfluxDB we are able to get insights in real time and act on.”
Using InfluxDB, ntopng is open to “big data” systems that can scale with data in volume and speed. It is able to export monitoring information in JSON format towards various systems including Elasticsearch/Logstash and ZMQ. ntopng is also able to collect, self-produce (from packets), and export monitoring information by normalizing it in JSON format.
Kubernetes monitoring made easy
Start using InfluxDB and Telegraf for Kubernetes monitoring for better visibility and earlier detection. Experience a faster time to awesome right now.
