Infrastructure Monitoring with New Relic: Hosts, Containers, and Cloud

Your apps are only as healthy as the infrastructure beneath them

Application metrics explain what is slow; infrastructure metrics often explain why. New Relic Infrastructure monitors the hosts, containers, and cloud services your code runs on — and correlates them with APM.

What It Captures

  • Host metrics — CPU, memory, disk, network per server
  • Processes — which process is eating resources
  • Containers and Kubernetes — pods, nodes, deployments
  • Cloud integrations — AWS, Azure, GCP managed services

On-Host Integrations

The infrastructure agent ships integrations for common services so you get tailored dashboards out of the box:

Integration Surfaces
nginx / Apache Requests, connections, worker status
PostgreSQL / MySQL Queries, locks, replication lag
Redis Memory, hit rate, evictions
Kubernetes Pod health, restarts, resource pressure

Correlating infra spikes with deploys turns guesswork into root cause

Installing the Agent

# Linux, one-line install
curl -Ls https://download.newrelic.com/install/newrelic-cli/scripts/install.sh | bash
sudo NEW_RELIC_API_KEY=xxxx NEW_RELIC_ACCOUNT_ID=12345 /usr/local/bin/newrelic install

Connecting Infra to APM

Because the same agent context links hosts to applications, you can jump from a slow transaction straight to the host’s CPU graph at that exact moment — the single most useful correlation in incident response.

Watch saturation, not just utilisation: a disk at 100% or memory near its limit predicts the next outage.

What to Learn Next

  • Kubernetes monitoring with the New Relic operator
  • Cloud cost and performance via cloud integrations
  • Alerting on host saturation before it cascades

Arivanandhan Chitheshwaran