openshift-docs/modules/serverless-queue-proxy-metrics.adoc

// Module is included in the following assemblies:
//
// * serverless/monitor/serverless-serving-metrics.adoc

:_content-type: REFERENCE
[id="serverless-queue-proxy-metrics_{context}"]
= Queue proxy metrics

Each Knative service has a proxy container that proxies the connections to the application container. A number of metrics are reported for the queue proxy performance.

You can use the following metrics to measure if requests are queued at the proxy side and the actual delay in serving requests at the application side.

[cols=5*,options="header"]
|===
|Metric name
|Description
|Type
|Tags
|Unit

|`revision_request_count`
|The number of requests that are routed to `queue-proxy` pod.
|Counter
|`configuration_name`, `container_name`, `namespace_name`, `pod_name`, `response_code`, `response_code_class`, `revision_name`, `service_name`
|Integer (no units)

|`revision_request_latencies`
|The response time of revision requests.
|Histogram
|`configuration_name`, `container_name`, `namespace_name`, `pod_name`, `response_code`, `response_code_class`, `revision_name`, `service_name`
|Milliseconds

|`revision_app_request_count`
|The number of requests that are routed to the `user-container` pod.
|Counter
|`configuration_name`, `container_name`, `namespace_name`, `pod_name`, `response_code`, `response_code_class`, `revision_name`, `service_name`
|Integer (no units)

|`revision_app_request_latencies`
|The response time of revision app requests.
|Histogram
|`configuration_name`, `namespace_name`, `pod_name`, `response_code`, `response_code_class`, `revision_name`, `service_name`
|Milliseconds

|`revision_queue_depth`
| The current number of items in the `serving` and `waiting` queues. This metric is not reported if unlimited concurrency is configured.
|Gauge
|`configuration_name`, `event-display`, `container_name`, `namespace_name`, `pod_name`, `response_code_class`, `revision_name`, `service_name`
|Integer (no units)
|===