CPU and memory
Track sustained pressure and trigger threshold-based alerts.
Monitor Type
Hardware Monitoring
Watch host-level resource health and infrastructure performance indicators.
What this monitor checks
Disk usage
Detect storage risks before they cause service disruption.
System state
Monitor host stability as part of incident diagnosis.
Common use cases
Capacity management
Catch saturation trends before customer impact.
Node stability
Identify unhealthy nodes quickly in distributed environments.
Infra incident triage
Provide fast context for on-call responders during host events.
Implementation blueprint
1. Define critical targets
Start with services and workflows that create direct customer or revenue impact.
2. Tune alert thresholds
Use warning and critical layers so on-call responders get signal without alert fatigue.
3. Validate escalation flow
Simulate failures and verify acknowledgement, assignment, and recovery behavior end-to-end.
Suggested thresholds
| Signal | Recommended baseline | Escalate when |
|---|---|---|
| CPU utilization | < 75% | > 90% for 10 minutes |
| Memory utilization | < 80% | > 92% for 10 minutes |
| Disk utilization | < 75% | > 90% sustained |
FAQ
Which hosts should be monitored first?
Prioritize nodes running customer-facing services, databases, and queue workers.
How can I reduce hardware alert fatigue?
Use sustained-duration thresholds and separate warning from critical conditions.
Should host alerts auto-create incidents?
For critical production systems yes; for lower tiers, route as warning first.
Related monitor types
Database Monitoring
Pair this monitor to increase coverage and improve incident triage confidence.
Custom Metrics Monitoring
Use together to reduce blind spots and catch degradation before customer impact.
Choose your preferred alert channels
Notify the right responders instantly across channels your team already uses.
Email and SMS
Deliver rapid alerts with fallback channels for critical incidents.
Slack and Teams
Route monitor events directly into team collaboration channels.
Webhooks and integrations
Trigger downstream workflows in PagerDuty, Opsgenie, and internal tools.
Advanced capabilities included
Multi-location monitoring
Run checks from multiple regions to isolate local routing issues from global outages.
Maintenance windows
Pause checks during planned maintenance to keep alert noise low and signal clear.
Recurring notifications
Keep stakeholders informed when incidents remain open for longer durations.
Status communication
Coordinate internal and customer updates with status page friendly incident workflows.
What teams value most
"We moved from delayed outage discovery to immediate, actionable alerts with clear ownership."
Deploy Hardware Monitoring checks quickly
Create your monitor, define escalation policy, and start getting reliable signal in minutes.