See every host, container, and node in one table
Uptrace auto-detects OpenTelemetry host metrics and activates a dashboard with zero configuration. CPU, memory, disk, filesystem, and network from every host, grouped by fleet and alertable like everything else in your stack.
14-day free trial · No credit card required
web-01web-02db-primaryworker-03cache-01db-replicaDashboards that build themselves
The moment Uptrace sees hostmetrics data, it activates a pre-built dashboard for CPU, memory, disk, and network, no manual setup, no YAML to write first.
- Auto-activating template ships with Uptrace and matches on incoming metric names
- Covers CPU utilization and time, memory usage, disk I/O, filesystem, network, and load average
- Same mechanism powers templates for PostgreSQL, MySQL, Redis, and Kubernetes
- Standard OpenTelemetry hostmetricsreceiver, no proprietary agent required
Every host in one table, not one dashboard per box
Table dashboards group by host_name so you see your whole fleet at a glance, then drill into a single row for that host's full timeseries.
- CPU, memory, disk, filesystem, and network from every scraper the collector runs
- Per-process metrics when you need them: CPU time and memory per process
- Resource detection tags every host with cloud provider, region, and hostname automatically
- Same PromQL-compatible query language as every other metric in Uptrace
Alert on any host metric
Host metrics are alertable the same way as spans and logs. Set a threshold once and route it through any of the eight notification channels covered on the alerting page.
- Metric monitors fire on threshold crossings for any hostmetrics series
- Group by host, region, or cloud provider to split noisy fleets into focused alerts
- Recovery notifications sent automatically when a host returns to normal
- See the full monitor and channel setup on the alerting page
Tag hosts with their real environment
The OpenTelemetry Resource Detection processor stamps every host with where it actually runs, so a query for "production, us-east" just works.
- Cloud metadata: AWS EC2, ECS, and EKS; GCP and GKE; Azure VMs and AKS
- Kubernetes pod, node, and namespace attributes for cluster-wide views
- Docker container metadata when running inside a container
- Filter or group any dashboard, monitor, or alert by these attributes
cloud.provideraws, gcp, azure, or none for bare metal
cloud.regionRegion or availability zone
k8s.pod.namePod, node, and namespace for cluster views
host.nameResolved via DNS, OS, or FQDN lookup
Better together
Each signal is more powerful when correlated with the others. Uptrace stores traces, logs, and metrics in one place, no tool-switching, no data gaps.
Common questions, clear answers
Do I need a special agent to monitor infrastructure?
Which metrics does infrastructure monitoring cover?
Do dashboards need to be configured manually?
Can I monitor hosts across multiple clouds in one view?
How is this different from the alerting product?
Ready to see your whole fleet in one table?
Deploy in minutes with Docker. Open source. Fixed pricing. Your data stays on your infrastructure.
Start monitoring your hosts14-day free trial · No credit card required
Learn more