Dashboards

Grafana Dashboard for Nginx Web Server.

USE (Utilization Saturation Errors) metrics dashboards for troubleshooting pod IP management in EKS

Grafana dashboard to display external-dns metrics

Latency and cache hit graphs for Kubernetes apiserver. Useful for observing performance of Amazon EKS clusters.

Visualize OpenTelemetry (OTEL) collector metrics (tested with OTEL contrib v0.156.0)

Cluster level overview of workloads deployed, based on prometheus metrics exposed by kubelet, node-exporter, nginx ingress controller

This dashboard gives overview of OpenEBS installation in cluster.

Display all useful Karpenter metrics

Prometheus monitoring for MSK cluster

Kubernetes Pods Log Monitoring and Insights Dashboard

Nomad cluster dashboard. Using built in nomad's exporter and loki. Example cluster is present there https://github.com/theztd/startup-infra-docker in

Windows Exporter Dashboard forked from Ismaeil Rasoulivand

Resource usage of Windows Containers/Pods in k8s

Node distribution on a number of axis (AZ, lifecycle, etc) + various other scaling metrics

Prometheus scrapes the ENI and IP information and aggregates it on the cluster level. Also, it requires annotations to be added to aws-node daemon set.

A Dashboard for the OpenFaaS serverless framework

ASP.NET Core metrics from OpenTelemetry

Summary metrics about containers running on Kubernetes nodes. Dashboard was taken from here. This version does not reqiure you to setup the Kubernetes-app plugin. (https://github.com/grafana/kubernetes-app) Use this Helm chart to launch Grafana into a Kubernetes cluster. It will include this dashboard and many more dashboards to give you visibility into the Kubernetes Cluster. (https://github.com/sekka1/cloud-public/tree/master/kubernetes/pods/grafana-helm)

Kubernetes Deployment Overview

Grafana dashboard to monitoring nodes grouped by AWS EKS nodegroup. Bear in mind you need a kubernetes label called "nodegroup" in each compute < Node Groups

Contains panels that show: 1. restarts per pod 2. oom killed processes in the node 3. pods that got oom killed

This dashboard will help you on maintaining a good TCO (Total Cost of Ownership) for your K8s cluster. You can analyse the overall resources usage Vs request and you can tweak the application resources accordingly. Currently the tables created are more focusing on the requests configured and its usages against the cluster resources. If the AVG request usage percentage is very less, your cluster is over provisioned. You need to tweak the resource request of your applications accordingly. T