Operations | Monitoring | ITSM | DevOps | Cloud

It’s 3 AM. API latency just spiked from 200ms to 2s. Alerts are firing, and users are frustrated. You SSH into the first server: top, free -h, iostat — nothing unusual. On to the next host. And the next. That’s how most of us learned to debug. The tools worked, and we got good at using them. But as infrastructure became distributed and dynamic, this approach started to break down. Modern monitoring needs more than SSH and top. It needs unified telemetry.

Application Performance Monitoring (APM) helps you understand how your software runs in production. When you track the right metrics, you see how requests move through your system, where slowdowns happen, and how resources are being used. With this knowledge, you can spot issues early and keep your applications reliable for your users. In this blog, we discuss the key APM metrics to monitor, grouped into categories, and why each one matters for performance and user experience.

Microservices make it tough to understand how applications behave end-to-end. Most teams already rely on an Application Performance Monitoring (APM) tool to track system health. But as requests move across many services, you also need distributed tracing. Jaeger gives you that visibility. The real value comes from connecting the two. Instead of running APM and Jaeger in silos, you can combine their strengths, metrics from your APM, and traces from Jaeger, to get a clearer view of performance.

You've got Prometheus running in one cluster — maybe a dev environment, a single EKS cluster, or a proof-of-concept setup. The configuration is straightforward: node_exporter on a few EC2 instances, some service discovery for pods, and a single Prometheus server scraping everything. Storage is local, retention is 15 days, and you can keep all the default recording rules without worrying about costs.

Modern applications don’t process everything inside the request/response path. To keep APIs responsive, time-consuming work like image resizing, payment processing, or data syncs is moved into background queues. Workers then pick up these asynchronous jobs and run them outside the main thread. Asynchronous job monitoring is the practice of tracking these background tasks: Without this visibility, background workers become a blind spot.

In Kubernetes, applications are constantly changing — new pods start, old ones shut down, workloads shift across nodes. The challenge is making sure that different parts of your system, and even external clients, can still find each other when the actual locations keep moving. That’s what service discovery handles. It provides a stable way for applications to connect and communicate, no matter where they’re running or how often the underlying infrastructure changes.

Databases handle critical operations for applications, from online banking to e-commerce and streaming services. Any slowdown or failure can directly affect application performance and user experience. Database monitoring tracks performance, detects issues, and helps prevent downtime. It also ensures efficient use of resources, maintains security, and supports compliance requirements.

Background jobs handle the critical work that happens outside the request path: processing payments, sending emails, generating reports, syncing data. They keep applications running smoothly, but the signals they produce look different from API endpoints. Most teams start with queue metrics—how many jobs are waiting and how quickly they complete. These metrics provide the foundation, but job health extends beyond throughput.

A service catalog gives teams a shared view of their systems—what services exist, who owns them, how dependencies are structured, and the SLAs that guide expectations. It’s an important part of development infrastructure because it helps everyone speak the same language about services. Service catalog observability builds on that foundation.