Infrastructure Monitoring Overview

SigNoz Cloud - This page applies to SigNoz Cloud editions.
Self-Host - This page applies to self-hosted SigNoz editions.

SigNoz Infrastructure Monitoring gives you a unified view of host and Kubernetes performance with correlated traces and logs. Use it to understand how infrastructure health impacts your applications and quickly drill from high-level lists into a single host, node, or pod.

Infrastructure Monitoring Dashboard
Set Up Infrastructure Monitoring in SigNoz with our Guided Onboarding

Start monitoring your infrastructure in 3 simple steps: First, choose your infrastructure data source (Host or Kubernetes). Then, configure OpenTelemetry Collector with our templates. Finally, visualize your infrastructure data in our comprehensive dashboards.

What is Infrastructure Monitoring in SigNoz

Infrastructure Monitoring provides real-time visibility into your physical/virtual machines and Kubernetes clusters. All data is collected via OpenTelemetry, giving you vendor-neutral instrumentation with full control over your telemetry pipeline.

Key capabilities

  • Host Monitoring: Monitor CPU, memory, disk, network, load average, and I/O wait across all hosts with color-coded progress bars, filtering, grouping, and drill-down into correlated traces and logs. The host list shows the same color-coded progress bars, and clicking any host opens detailed metrics, traces, and logs.
  • Kubernetes Monitoring: Monitor Pods, Containers, Nodes, Namespaces, Clusters, Deployments, Jobs, DaemonSets, StatefulSets, and Volumes with resource utilization, workload health, and correlated traces, logs, and events. Switch between resource types using the sidebar; clicking any entity opens its detailed metrics, traces, logs, and events.
  • Correlated Signals: Host detail pages include Metrics, Logs, and Traces tabs; most Kubernetes entity detail pages add an Events tab on top of that (Volumes shows Metrics only). Move between signals without losing context.
  • Flexible Filtering: Filter by any resource attribute, group by attributes like os.type or k8s.namespace.name, and customize visible columns.

Get started

Reference

Last updated: August 03, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.