For CA Application Performance Management (APM), a common term used with APM Operational Adoption is Key Performance Metrics, or KPMs.
In simplistic terms, a KPM is a measurable value that demonstrates how effectively a software application or Business Service is performing, from a usability or reliability perspective, for the consumer or end user. company is achieving key business objectives.
KPMs help determine the ‘state’ of the application or business service by collecting metrics for each component used. A component could be a servlet, web page, an external call (i.e., web service), script, or any other function that makes up the application. All of the components, banded together, make up the application or service.
Examples of commonly used KPMs
One example of commonly used KPMs are called resource metrics. These metrics are a collection of system, infrastructure, or configuration metrics that affect the behavior of the application. For example, the time in garbage collection for a JVM heap can be used as a resource metric that could affect application performance.
Another example of KPMs are called application performance metrics. These metrics represent a collection of application component-level metrics; average response time, concurrent invocations, responses per interval, stalls, or errors. For example, a backend database SQL call, launched from the application tier, can affect overall application performance if the call is slow or problematic.
CA Lead Practices for KPMs
Naturally, each application is different in the way it consumes or ingests data. As part of the CA APM Operational Adoption Service, CA can help review and guide you to effectively tune alerts and associated thresholds based on our Lead Practices. There are several recommended starting points to standardize your alert implementations, let CA Services help you gain value from your monitoring implementation.