Gathering and reviewing metrics derived from the state of Kubernetes resources can help you understand performance and possible bottlenecks.

Why use the Kubernetes Inventory Telegraf Plugin

The Kubernetes Inventory Telegraf Plugin generates metrics derived from the state of your Kubernetes resources. These metrics will help you to manage your resources so you can understand which machines are related to which teams.

How to use the Kubernetes Inventory Telegraf Plugin

To use the Kubernetes Inventory Telegraf Plugin, customize the configuration to suit your monitoring needs:

  • The URL for the Kubernetes API
  • Namespace to use
  • Bearer token for authorization
  • Response timeout
  • Optional resources to exclude from metric collection
  • Optional TLS configuration

If you are using RBAC, you will need to create a cluster role to list "persistentvolumes" and "nodes". You will also need to make an aggregated ClusterRole that will eventually be bound to a user or group.

You can also use this plugin to monitor K3S server instances by using the auto-generated administration token. This is less secure than using the more restrictive dedicated Telegraf user but more convenient to set up.

For more information, please check out the documentation.

Project URL   Documentation

Related resources

Scaling Kubernetes Deployments with InfluxDB & Flux

Learn how to deploy the kube-metrics-adapter to your cluster to control the scaling of your resources.

Nginx Ingress Controller Template

Monitor your Nginx Controller setup inside your Kubernetes cluster.

Prometheus Remote Write Support

Telegraf includes a Prometheus remote write parser that can be used to ingest metrics and output them to InfluxDB 1.x or InfluxDB 2.0.

Scroll to Top