feat(docs): Add Karpenter Monitoring docs

constants/listicles/dashboard-templates.json

@@ -361,6 +361,12 @@
       "clickName": "Kafka Dashboard Template",
       "icon": "/img/icons/listicle/si-kafka.svg"
     },
+    {
+      "name": "Karpenter",
+      "href": "/docs/dashboards/dashboard-templates/karpenter-dashboard",
+      "clickName": "Karpenter Dashboard Template",
+      "icon": "/img/icons/listicle/karpenter.svg"
+    },
     {
       "name": "Kubernetes",
       "href": "/docs/dashboards/dashboard-templates/kubernetes-dashboards",

constants/listicles/metrics-quick-start.json

@@ -193,6 +193,12 @@
           "clickName": "KEDA Metrics Link",
           "icon": "/img/icons/listicle/lucide-zap-purple.svg"
         },
+        {
+          "name": "Karpenter",
+          "href": "/docs/metrics-management/opentelemetry-karpenter-metrics",
+          "clickName": "Karpenter Metrics Link",
+          "icon": "/img/icons/listicle/karpenter.svg"
+        },
         {
           "name": "OpenTelemetry Collector",
           "href": "/docs/metrics-management/opentelemetry-collector-metrics",

data/docs-side-nav/main.json

@@ -2104,6 +2104,11 @@
                 "route": "/docs/metrics-management/istio-metrics",
                 "label": "Istio Metrics"
               },
+              {
+                "type": "doc",
+                "route": "/docs/metrics-management/opentelemetry-karpenter-metrics",
+                "label": "Karpenter Metrics"
+              },
               {
                 "type": "doc",
                 "route": "/docs/metrics-management/nginx-ingress-controller",
@@ -2911,6 +2916,11 @@
             "route": "/docs/dashboards/dashboard-templates/kafka-dashboard",
             "label": "Kafka"
           },
+          {
+            "type": "doc",
+            "route": "/docs/dashboards/dashboard-templates/karpenter-dashboard",
+            "label": "Karpenter"
+          },
           {
             "type": "doc",
             "route": "/docs/dashboards/dashboard-templates/keda",

data/docs/aws-monitoring/eks/eks-ec2-nodes.mdx

@@ -69,6 +69,7 @@ Once installed, your EKS data will appear in:
 - [K8s-Infra Installation Guide](https://signoz.io/docs/opentelemetry-collection-agents/k8s/k8s-infra/install-k8s-infra/) – Detailed installation instructions.
 - [Configure K8s-Infra](https://signoz.io/docs/opentelemetry-collection-agents/k8s/k8s-infra/configure-k8s-infra/) – Customize log filtering, metrics collection, and more.
 - [Infrastructure Monitoring Overview](https://signoz.io/docs/infrastructure-monitoring/overview/) – Learn about the Infrastructure Monitoring module features.
+- [Send Karpenter Metrics to SigNoz](https://signoz.io/docs/metrics-management/opentelemetry-karpenter-metrics/) – If Karpenter provisions these nodes, monitor its provisioning and consolidation decisions.
 
 </TabItem>
 <TabItem value="one-click" label="One-Click Integration">

data/docs/dashboards/dashboard-templates/karpenter-dashboard.mdx

@@ -0,0 +1,114 @@
+---
+date: 2026-08-31
+title: Karpenter Metrics Dashboard for Kubernetes Autoscaling
+description: Monitor Karpenter node autoprovisioning in SigNoz including provisioning latency, disruption, scheduling, cloud provider health, and NodePool cost.
+doc_type: explanation
+---
+
+Use this dashboard to monitor Karpenter across fleet size and utilization, provisioning and scheduling, disruption and consolidation, controller and cloud provider health, Spot interruption, and NodePool capacity and cost.
+
+Karpenter exposes native `karpenter_*` metrics on the controller metrics endpoint, and the OpenTelemetry Collector scrapes them for this dashboard.
+
+<Admonition type="note">
+Set up the data source and send telemetry to SigNoz before you import this dashboard. Follow the [Send Karpenter Metrics to SigNoz](https://signoz.io/docs/metrics-management/opentelemetry-karpenter-metrics/) guide.
+</Admonition>
+
+<Figure
+  src="/img/docs/dashboards/dashboard-templates/karpenter-dashboard.webp"
+  alt="Karpenter Metrics Dashboard"
+  caption="Karpenter Metrics Dashboard"
+/>
+
+<DashboardActions
+  dashboardJsonV2Url="https://raw.githubusercontent.com/SigNoz/dashboards/refs/heads/main/karpenter/karpenter-dashboard.json"
+  dashboardName="Karpenter"
+/>
+
+## Dashboard Coverage
+
+Use these panels to:
+
+- **Confirm fleet state**: See how many nodes Karpenter tracks, how many it owns against the rest of the cluster, whether its view of the cluster is synced, and which build is running.
+- **Watch provisioning**: Track node and NodeClaim creation by NodePool and zone, scheduler queue depth, and how long pods wait to bind and start.
+- **Find unschedulable work**: Monitor pods Karpenter cannot place, and pending pods grouped by their effective zone constraint.
+- **Follow disruption**: Track disruption decisions by reason and NodePool, nodes eligible for disruption, budget consumption, and drain and termination activity.
+- **Check controller health**: Watch cloud provider call latency, call rate, error rate by method, and how long cluster state stays unsynced.
+- **Handle Spot interruption**: Track interruption messages by type and how long they sit on the queue before Karpenter processes them.
+- **Review capacity and cost**: Compare NodePool usage against configured limits, pod requests against allocatable, system overhead, and Karpenter's hourly cost estimate.
+
+## Metrics Included
+
+### Fleet Overview
+
+- **Nodes in Cluster State**: Nodes Karpenter tracks.
+- **Cluster State Synced**: `1` when Karpenter's view matches the API server.
+- **Karpenter-Managed Nodes**: Nodes Karpenter provisioned.
+- **Unschedulable Pods**: Pods Karpenter cannot place.
+- **Cluster Utilization by Resource**: Pod requests as a percentage of allocatable.
+- **Allocatable CPU: Karpenter-Managed vs Unmanaged**: Capacity split by the `managed` label.
+- **Karpenter Build Info**: Running version, Go version, and architecture.
+
+### Provisioning & Scheduling
+
+- **Nodes Created** and **NodeClaims Created**: Provisioning activity by NodePool, zone, and reason.
+- **Scheduler Queue Depth**: Pods waiting for a scheduling decision.
+- **Unschedulable Pods Over Time**: Unschedulable count by controller.
+- **Pending Pods by Effective Zone**: Pending pods by zone constraint.
+- **Pod Bound Duration**: p50, p95, and p99 time from pod creation to binding.
+- **Pod Provisioning Startup Duration (p95)**: Time from Karpenter deciding a pod can schedule until it runs.
+- **Longest Pod Unbound Wait by Namespace**: Age of the oldest unbound pod per namespace.
+- **Pods by Phase**: Pod counts by phase.
+
+### Disruption & Consolidation
+
+- **Disruption Decisions by Decision & Reason** and **by NodePool**: Voluntary disruption actions taken.
+- **Nodes Eligible for Disruption by Reason**: Nodes currently eligible, by reason.
+- **Allowed Disruptions by NodePool & Reason** and **Nodes Consuming Disruption Budget**: Budget headroom and usage.
+- **Nodes Drained** and **Nodes Terminated**: Drain and termination counts by NodePool and zone.
+- **NodeClaims Disrupted by Reason** and **NodeClaims Terminated**: NodeClaim-level disruption and removal.
+- **Disruption Decision Evaluation Duration**: p50 and p95 time to evaluate a disruption decision.
+- **Consolidation Timeouts**: Times the consolidation algorithm hit its timeout.
+- **NodeClaim Termination Duration (p95)**: Time to fully terminate a NodeClaim.
+
+### Controller & Cloud Provider Health
+
+- **CloudProvider Error Rate by Method & Error**: Failed cloud API calls.
+- **CloudProvider Call Latency by Method**: p50 and p95 latency per cloud API method.
+- **CloudProvider Call Rate by Method**: Call throughput per method.
+- **Cluster State Unsynced Time**: How long Karpenter's state has been out of sync.
+- **Scheduling Simulation Duration by Controller**: p50 and p95 scheduling simulation time.
+
+### Spot Interruption
+
+- **Interruption Messages Received by Type**: Spot interruption and instance health notices by message type.
+- **Interruption Message Queue Duration (p95)**: Time a message waits on the SQS queue before Karpenter handles it.
+
+### Capacity & Cost
+
+- **NodePool Usage as % of Limit**: Provisioned resources against configured NodePool limits.
+- **NodePool Hourly Cost Estimate**: Karpenter's current hourly cost estimate for a NodePool. This is not a billing source.
+- **CPU Requests as % of Allocatable**: Pod requests against allocatable, split by `managed`.
+- **Node System Overhead**: Resources reserved for system overhead.
+- **Oldest Karpenter Node Age by NodePool**: Age of the longest-lived Karpenter node.
+
+## Dashboard Variables
+
+Use these filter variables:
+
+- **nodepool**: Filter by Karpenter NodePool name.
+- **capacity_type**: Filter by `on-demand`, `spot`, or `reserved`.
+- **zone**: Filter by availability zone.
+
+## Notes
+
+- **The Spot Interruption panels need an interruption queue.** They stay empty unless you set `settings.interruptionQueue` to an SQS queue name when installing Karpenter.
+- **Only the leader replica emits most metrics.** Karpenter runs two replicas with leader election. No panel groups by pod, so each one stays correct whichever replica holds the lease.
+- **Some panels are deliberately unfiltered.** `karpenter_nodes_*` and `karpenter_pods_state` cover every node and pod in the cluster, not only Karpenter's. Unmanaged nodes carry an empty `nodepool` and `capacity_type`, so filtering those panels would silently drop them.
+- **Counter panels use `increase`, which needs two datapoints.** Karpenter's labeled counters do not exist until their first increment, so a first-ever event on a new cluster does not register. Later events do.
+- **The instance type catalog metrics are excluded.** `karpenter_cloudprovider_instance_type_offering_available` and `_price_estimate` emit one series per instance type, zone, and capacity type in the region, and do not scale with cluster size. See the [cardinality guidance](https://signoz.io/docs/metrics-management/opentelemetry-karpenter-metrics/#key-metrics) in the setup guide.
+
+## Related Dashboards
+
+- [Cert-Manager](https://signoz.io/docs/dashboards/dashboard-templates/cert-manager-dashboard/)
+- [KEDA](https://signoz.io/docs/dashboards/dashboard-templates/keda/)
+- [Hostmetrics and Kubernetes](https://signoz.io/docs/dashboards/dashboard-templates/hostmetrics-k8s/)

data/docs/infrastructure-monitoring/kubernetes/nodes.mdx

@@ -148,3 +148,4 @@ Click a node name to open the detail page. The header shows **Node Name** and **
 - [Kubernetes Monitoring](https://signoz.io/docs/infrastructure-monitoring/kubernetes-monitoring/): back to the Kubernetes Monitoring overview.
 - [Setup Kubernetes Metrics](https://signoz.io/docs/infrastructure-monitoring/user-guides/k8s-metrics/): configure the receivers this page's metrics depend on, including the optional allocatable metrics.
 - [Pods](https://signoz.io/docs/infrastructure-monitoring/kubernetes/pods/) and [Clusters](https://signoz.io/docs/infrastructure-monitoring/kubernetes/clusters/): drill into the workloads running on these nodes or roll up to the cluster level.
+- [Send Karpenter Metrics to SigNoz](https://signoz.io/docs/metrics-management/opentelemetry-karpenter-metrics/): if Karpenter manages your nodes, see why they were provisioned and when they get consolidated away.

data/docs/metrics-management/keda-metrics.mdx

@@ -208,6 +208,7 @@ For more details, see [Why use the OpenTelemetry Collector?](https://signoz.io/d
 - **Set Alerts**: Configure alerts to get notified when scaler errors spike or scaling latency increases. [Learn more](https://signoz.io/docs/alerts-management/metrics-based-alerts/).
 - **Create Dashboards**: Build dashboards to visualize scaling loop latency, active scalers, and error rates across your ScaledObjects.
 - **Learn more about KEDA**: Visit the <a href="https://keda.sh/docs/latest/integrations/opentelemetry/" target="_blank" rel="noopener noreferrer nofollow">KEDA OpenTelemetry Integration docs</a> for additional configuration options.
+- **Monitor node autoscaling too**: KEDA scales pods, and [Karpenter](https://signoz.io/docs/metrics-management/opentelemetry-karpenter-metrics/) scales the nodes those pods land on. Monitoring both shows whether pending pods are waiting on a scaling decision or on capacity.
 
 ## Get Help