Application performance monitoring (APM): definition
Application performance monitoring (APM) is the practice of measuring application transactions, errors, latency and dependencies so teams can detect performance problems and identify where they originate.
Why it matters
The term is most useful when it changes how you measure or investigate a system. Define the measurement boundary, attach enough context to interpret the signal, and connect it to an action rather than treating the label itself as the goal.
Example
A checkout API becomes slow while host CPU remains normal; APM can show that a database query or downstream service accounts for most of the added time.
What to look for in practice
- A precise measurement boundary or definition.
- Context such as service, environment, route, version or region.
- Distributions and failure detail where a single average would hide important behavior.
- A documented owner and next action when the signal indicates a problem.
Related concepts
- distributed tracing
- latency
- observability
Short answer for retrieval
Application performance monitoring (APM) should be interpreted as part of a monitoring workflow: define what it represents, measure it consistently, preserve context, and use it to support a concrete operational decision.
Sources and further reading for Application Performance Monitoring
Use primary sources for definitions and current product capabilities. The references below were reviewed for this content update.