What's included?
alerts
18
Kubernetes (OpenTelemetry) observability quickstart contains 18 alerts. These alerts detect changes in key performance metrics. Integrate these alerts with your favorite tools (like Slack, PagerDuty, etc.) and New Relic will let you know when something needs your attention.
More than 5 pods failing in namespace
Alert when more than 5 pods are failing in a namespace for more than 5 minutes
Persistent Volume has errors
Alert when Persistent Volume is in a Failed or Pending state for more than 5 minutes
Node is not ready
Alert when a Node is not ready for > 5 minutes
Pod cannot be scheduled
Alert when a Pod cannot be scheduled for more than 5 minutes
Container is Restarting
Alert when the container restart count is greater than 0 in a sliding 5 minute window
Statefulset is missing Pods
Alert when Statefulset is missing Pods for > 5 minutes
Node root file system capacity utilization is high
Alert when the average Node root file system capacity utilization is > 90% for more than 5 minutes
Container high cpu utilization
Alert when the average container cpu utilization (vs. Limit) is > 90% for more than 5 minutes
Container cpu throttling is high
Alert when container is being throttled > 25% of the time for more than 5 minutes
Container is Waiting
Alert when a container is Waiting for more than 5 minutes
Node allocatable cpu utilization is high
Alert when the average Node allocatable cpu utilization is > 90% for more than 5 minutes
Pod is not ready
Alert when a Pod is not ready for > 5 minutes
Deployment is missing Pods
Alert when Deployment is missing Pods for > 5 minutes
Daemonset is missing Pods
Alert when Daemonset is missing Pods for > 5 minutes
Node Pod count nearing capacity
Alert when the Running pod count on a Node is > 90% of the Node's Pod Capacity for more than 5 minutes
Job Failed
Alert when a Job reports a failed status
Container high memory utilization
Alert when the average container memory utilization (vs. Limit) is > 90% for more than 5 minutes
Node allocatable memory utilization is high
Alert when the average Node allocatable memory utilization is > 90% for more than 5 minutes
documentation
1
Kubernetes (OpenTelemetry) observability quickstart contains 1 documentation reference. This is how you'll get your data into New Relic.
dashboards
0
This quickstart doesn't include any dashboards. Do you think it should?
You can edit this quickstart to add helpful components. View the repository and open a pull request.
You can edit this quickstart to add helpful components. View the repository and open a pull request.
View repo
View repo
Why monitor Kubernetes using OpenTelemetry?
Kubernetes is an open-source system for automating deployment, scaling, and, management of containerized applications. OpenTelemetry is an open source observability framework that provides IT teams with standardized protocols and tools for collecting and routing telemetry. Organizations adopting OpenTelemetry will get advantage of vendor neutrality by using flexible and open-source agents and/or SDKs.
New Relic provides OpenTelemetry observability for Kubernetes which aims not only to ingest all the data sent but also to provide first-class K8s experiences and insights.
This quicktart gives you visibility into your Kubernetes clusters and workloads in minutes, whether your clusters are hosted on-premises or in the cloud.
Kubernetes (OpenTelemetry) quickstart highlights
Included in this quickstart you will find:
- Instructions to install our K8s instrumentation with OpenTelemetry.
- A complete recommended alert policy including alert conditions to be notified on most of the common relevant issues.
- Container CPU throttling is high (alert condition)
- Container high CPU utilization (alert condition)
- Container high memory utilization (alert condition)
- Container is restarting (alert condition)
- Container is waiting (alert condition)
- Daemonset is missing pods (alert condition)
- Deployment is missing pods (alert condition)
- Etcd fie descriptor utilization is high (alert condition)
- Etcd has no leader (alert condition)
- HPA current replicas < desired replicas (alert condition)
- HPA has reached maximum replicas (alert condition)
- Job Failed (alert condition)
- More than 5 pods failing in namespace (alert condition)
- Node allocatable CPU utilization is high (alert condition)
- Node allocatable memory utilization is high (alert condition)
- Node is not ready (alert condition)
- Node is unschedulable (alert condition)
- Node pod count nearing capacity (alert condition)
- Node root file system capacity utilization is high (alert condition)
- Persistent volume has errors (alert condition)
- Pod cannot be scheduled (alert condition)
- Pod is not ready (alert condition)
- Statefulset is missing pods (alert condition)