Kube Enrichment allows you to view your Kube events and metrics alongside your logs, all within LogDNA. With your Kube 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.
While Kube Enrichment is in early access, you’ll need to be invited and have the feature enabled on your account before continuing. Learn more about the early access program here.
- 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.
To get started with Kube Enrichment, you’ll have to add an additional LogDNA reporter to your Kube cluster. You can easily deploy the LogDNA reporter by applying the following deployment configuration.
kubectl apply -f https://repo.logdna.com/logdna-reporter/logdna-reporter.yaml
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 Kube metrics in your 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 Kube 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.
Kube Enrichment comes pre-bundled with views to categorize and surface Kube events. With your Kube events being retained in LogDNA, you can easily find and view historical or current kube events.
View Events in Context
Kube 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)
Using the Screens included in Kube Enrichment, you can have an overview of cluster-level metrics and identify anomalous behavior in your cluster.
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.
While Kube Enrichment is in early access, you’ll need to be invited and have the feature enabled on your account before continuing.
During the early access, metric features of Kube Enrichment will come at no additional cost. As an early access participant, you’ll be the first to know of any changes to the pricing structure well ahead of when they’ll take effect.
As part of Kube Enrichment, the reporter will pull in additional Kube event logs which will count against your current storage retention. The volume of logs associated with Kube events will vary depending on the activity level of the cluster. You’ll always be able to leverage exclusion rules to exclude certain events from counting towards your retention.
You can opt out at any time, just let us know you’d like to leave the early access program and we’ll disable the feature on your account and help you uninstall the reporter.
As an early access participant, we’d love to hear your feedback and we will reach out to select participants to learn more about how you’re using Kube Enrichment and how we can better align it with your team’s use cases.
The Kube 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.
To verify if you have
kubectl get deployment metrics-server -n kube-system
NAME READY UP-TO-DATE AVAILABLE AGE metrics-server 1/1 1 1 9s
Updated 13 days ago