Kubernetes Enrichment

View your Kubernetes events and metrics alongside your logs, all within LogDNA

LogDNA EnterpriseLogDNA Enterprise

What is Kubernetes Enrichment?

Kubernetes Enrichment allows you to view your Kubernetes events and metrics alongside your logs, all within LogDNA. With your Kubernetes events, metrics and application logs all in one place, you’ll be able to pinpoint issues faster and skip the context switching between logs and other tools.

Easily view metrics such as CPU, memory, ready status as well as other metadata such as image version and uptime without ever leaving the log viewer.

Getting Started with Kubernetes Enrichment

Kubernetes Enrichment is an Enterprise-level feature, you’ll need to be part of an Enterprise-level plan and reach out to your account's dedicated Customer Success Manager to get started. There are no additional costs for our Enterprise-level customers. If you're not an Enterprise-level customer and would like to learn more, contact our sales team ([email protected]).


  • Kubernetes version 1.8+.
  • LogDNA Agent for Kubernetes installed and running in your cluster.
  • Kubernetes Metrics Server installed on your Kubernetes cluster. If you’re on GKE or AKS, your deployment will automatically have the metrics server installed. If you don’t have the metrics server installed or not sure if you have it installed, click here to learn more.

Installing the LogDNA Reporter

To install the LogDNA Reporter, reach out to your Customer Success Manager for installation instructions.

After deploying the reporter, you should see metrics attached to your logs in a few minutes. Continue to the next section to learn how to see Kubernetes metrics in your logs.

Viewing Kubernetes Metrics in Logs

Once you set up the LogDNA reporter, you can start viewing metrics directly in the log viewer context menu. These metrics and metadata all show a point in time capture of the Kubernetes cluster state when that log line was sent, so even if an event happened a few days ago, the metrics will still reflect what was happening during that event.

Clicking the arrow under kube stats will further show the node information along with the pod image, namespace, and controller. You can use this information to quickly understand resource constraints, unstable pod deployments, or unhealthy nodes when that log line was sent. All metrics would have the same retention as your log retention today and metrics are currently collected every 30 seconds.

Viewing Kubernetes Event Logs

Kubernetes Enrichment comes pre-bundled with views to categorize and surface Kubernetes events. With your Kubernetes events being retained in LogDNA, you can easily find and view historical or current Kubernetes events.


View Events in Context

Kubernetes events combined with “View In Context” allow you to quickly see the log lines preceding a specific event (ex. What an application was logging before it was killed)

Viewing Kubernetes Cluster-Wide Health

Using the Screens included in Kubernetes Enrichment, you can have an overview of cluster-level metrics and identify anomalous behavior in your cluster.


Multi-Cluster Users

For multi-cluster users, you can filter down each dashboard to a specific cluster by using the _tag:<tagname> filter if you have cluster specific tags set up.

Note: Screens may take up to 24 hours to populate with metrics.

Installing or Verifying the Kubernetes Metrics Server Prerequisite

The Kubernetes metrics server is installed by default if you’re using Google Kubernetes Engine (GKE), IBM Cloud Kubernetes Service, or Azure Kubernetes Service (AKS) of at least version 1.10.

For other providers you can find instructions on how to install metrics-server here:
AWS Elastic Kubernetes Service
IBM Kubernetes Service
Kubernetes Installation Manifest

To verify if you have metrics-server installed:

kubectl get deployment metrics-server -n kube-system


metrics-server   1/1     1            1           9s

Updated 15 days ago

Kubernetes Enrichment

View your Kubernetes events and metrics alongside your logs, all within LogDNA

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.