Metrics at the Prometheus Scrape Endpoint
PingGateway exposes a monitoring endpoint where Prometheus can scrape metrics in a standard Prometheus format. Learn more from the Prometheus website.
When PingGateway is set up as described in the Getting started with PingGateway, the Prometheus Scrape Endpoint is available by default at http://ig.example.com:8085/metrics/prometheus/0.0.4.
Learn to query the Prometheus Scrape Endpoint in Monitor the Prometheus Scrape Endpoint.
Some |
Name | Type | Description |
---|---|---|
|
Summary |
Distribution of 'COLLECTED' eviction events |
|
Summary |
Distribution of 'COLLECTED' eviction events |
|
Counter |
Number of times the cache has been asked for a value and a value was found |
|
Summary |
Track time spent loading entries unsuccessfully; the 'content' label is one of: 'access_token', 'policy_decision', 'session', 'user_profile' |
|
Summary |
Track time spent loading entries unsuccessfully; the 'content' label is one of: 'access_token', 'policy_decision', 'session', 'user_profile' |
|
Summary |
Track time spent loading entries unsuccessfully; the 'content' label is one of: 'access_token', 'policy_decision', 'session', 'user_profile' |
|
Gauge |
Number of connections to the remote host currently open |
|
Gauge |
Number of requests waiting for a response |
|
Gauge |
Number of websockets currently open |
|
Counter |
Number of bytes received from the remote host |
|
Counter |
[Deprecated] Number of bytes received from the remote host |
|
Counter |
Number of bytes sent to the remote host |
|
Counter |
[Deprecated] Number of bytes sent to the remote host |
|
Gauge |
Number of pending elements in queue [DEPRECATED] |
|
Summary |
Time spent in queue before being processed |
|
Summary |
Time spent in queue before being processed |
|
Summary |
Time spent in queue before being processed [DEPRECATED] |
|
Summary |
Size of requests in bytes |
|
Summary |
Size of requests in bytes |
|
Counter |
Number of requests sent |
|
Counter |
[Deprecated] Number of requests sent |
|
Summary |
Size of responses in bytes |
|
Summary |
Size of responses in bytes |
|
Summary |
Response time |
|
Summary |
Response time |
|
Summary |
Response time |
|
Counter |
Response count with codes |
|
Counter |
[Deprecated] Response count with codes |
|
Gauge |
Number of open connections to the server |
|
Gauge |
Number of requests being processed |
|
Gauge |
Number of websockets currently open |
|
Counter |
Number of bytes received by the server |
|
Counter |
[Deprecated] Number of bytes received by the server |
|
Counter |
Number of bytes sent by the server |
|
Counter |
[Deprecated] Number of bytes sent by the server |
|
Summary |
Size of requests in bytes |
|
Summary |
Size of requests in bytes |
|
Counter |
Number of request resets |
|
Counter |
[Deprecated] Number of request resets |
|
Counter |
Number of processed requests |
|
Counter |
[Deprecated] Number of processed requests |
|
Summary |
Size of responses in bytes |
|
Summary |
Size of responses in bytes |
|
Summary |
Request processing time |
|
Summary |
Request processing time |
|
Summary |
Request processing time |
|
Gauge |
Number of processors available to the Java virtual machine |
|
Counter |
Number of classes loaded since the Java virtual machine started |
|
Counter |
Number of classes unloaded since the Java virtual machine started |
|
Gauge |
Bytes of free memory allocated to the Java virtual machine |
|
Counter |
Total number of garbage collections since startup |
|
Counter |
Approximate accumulated garbage collection elapsed time in milliseconds |
|
Gauge |
Maximum amount of memory that the Java virtual machine will attempt to use |
|
Gauge |
Amount of memory guaranteed to be available to the Java virtual machine |
|
Gauge |
Amount of memory the Java virtual machine requested during startup |
|
Gauge |
Maximum amount of memory the Java virtual machine can use for memory management |
|
Gauge |
Amount of memory guaranteed to be available to this memory pool |
|
Gauge |
Amount of memory the memory pool requested during startup |
|
Gauge |
Maximum amount of memory the memory pool can use for memory management |
|
Gauge |
Amount of memory the memory pool uses after the most recent garbage collection |
|
Gauge |
Amount of memory the memory pool currently uses |
|
Gauge |
Maximum amount of memory the Java virtual machine currently uses |
|
Gauge |
Number of live daemon threads |
|
Gauge |
Number of threads in the specified state |
|
Gauge |
Amount of memory used by the Java virtual machine |
|
Counter |
Number of elements done with the resource |
|
Counter |
[Deprecated] Number of elements done with the resource |
|
Gauge |
Number of resources used |
|
Gauge |
Number of resources used |
|
Gauge |
Number of pending elements in queue |
|
Summary |
Time spent in queue before being processed |
|
Summary |
Time spent in queue before being processed |
|
Summary |
Time spent in queue before being processed |
|
Gauge |
Pool usage ratio, only meaningful if maximum pool size could be determined |
|
Summary |
Time using a resource |
|
Summary |
Time using a resource |
|
Summary |
Time using a resource |
|
Counter |
Number of application side websocket proxy frames received1 |
|
Counter |
Number of application side websocket proxy frames received1 |
|
Counter |
Number of application side websocket proxy frames sent1 |
|
Counter |
Number of application side websocket proxy frames sent1 |
|
Counter |
Number of client side websocket proxy frames received1 |
|
Counter |
Number of client side websocket proxy frames received1 |
|
Counter |
Number of client side websocket proxy frames sent1 |
|
Counter |
Number of client side websocket proxy frames sent1 |
|
Gauge |
Number of active websocket proxy tunnels1 |
|
Gauge |
Number of active websocket proxy tunnels1 |
|
Counter |
Number of created websocket proxy tunnels1 |
|
Counter |
Number of created websocket proxy tunnels1 |
|
Gauge |
Number of requests being processed |
|
Counter |
Number of requests processed by the router or route since it was deployed |
|
Counter |
Number of responses that threw an exception |
|
Counter |
Number of responses that were not handled by the route |
|
Counter |
Number of responses by HTTP status code family. The 'family' label depends on the HTTP status code |
|
Summary |
Response time observations |
|
Summary |
Response time observations |
|
Summary |
Response time observations |
|
Gauge |
Number of routes deployed in the configuration |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Top-level startup metrics2 |
|
Summary |
Time to process the request and response in the decorated filter (downstream time) |
|
Summary |
Time to process the request and response in the decorated filter (downstream time) |
|
Summary |
Time to process the request and response in the decorated filter (downstream time) |
|
Summary |
Time to process the request and response in the decorated filter (elapsed time) |
|
Summary |
Time to process the request and response in the decorated filter (elapsed time) |
|
Summary |
Time to process the request and response in the decorated filter (elapsed time) |
|
Summary |
Time to process the request and response in the decorated filter (internal time) |
|
Summary |
Time to process the request and response in the decorated filter (internal time) |
|
Summary |
Time to process the request and response in the decorated filter (internal time) |
|
Summary |
Time to process the request and response in the decorated handler |
|
Summary |
Time to process the request and response in the decorated handler |
|
Summary |
Time to process the request and response in the decorated handler |
1 The "reverseproxyhandler" in the metric name reflects the name of the ReverseProxyHandler component in the PingGateway configuration.
2 The present implementation includes the deprecated parentId
and parentKind
dimensions.
Use the equivalent parent_id
and parent_kind
dimensions instead.