ERS Metrics

MTG ERS exposes Prometheus metrics for application resource usage, request processing, authentication and proxy traffic. Use the component references to interpret metric names, units and labels in your monitoring queries and dashboards.

Components

Component Endpoint Metric reference

CLM server

/actuator/prometheus on port 9090

Java Service Metrics, including database-pool metrics.

ACME

/actuator/prometheus on port 9090

Java Service Metrics, including database-pool metrics.

AEC, CMP, EST, and SCEP

/actuator/prometheus on port 9090

Java Service Metrics.

CARA WS server

/actuator/prometheus on port 9090

Java Service Metrics, including database-pool metrics.

Revocation Information Service

/actuator/prometheus on port 9090

Java Service Metrics.

Keycloak

/auth/metrics on port 9000

Authentication, cache, database, and runtime metrics.

HAProxy

/metrics on port 1042

Traffic, connection, health-check, and DNS metrics.

CLM UI and CARA Admin UI

No application metrics endpoint

Monitor application traffic through HAProxy and workload availability through the appliance dashboards.

Metric values

A counter accumulates events or quantities. Use its rate of change to measure activity over an interval.

A gauge reports a current value, such as memory use or the number of active connections.

A timer records event counts and durations. Labels distinguish series for routes, response outcomes, memory pools, database pools, caches and proxy backends.

For completed operations, timer samples ending in _count and _sum contain cumulative observations and duration. For active operations, these samples describe work still in progress and can decrease as operations finish. For Java service timers, _max reports a rolling maximum. HAProxy timing metrics report averages and recorded maxima.