Prometheus metrics¶
Anbox Cloud gathers various performance metrics that you can access through API endpoints.
The following sections list all metrics for each service endpoint.
AMS¶
The Anbox Management Service provides metrics about the Anbox Cloud cluster (or the Anbox Cloud Application server) and the AMS API access.
Objects¶
Metrics prefixed with ams_cluster_
keep you informed about the status of your Anbox Cloud cluster.
Name |
Description |
Status |
---|---|---|
|
Number of nodes in the cluster |
Available since 1.0.0 |
|
Number of applications |
Available since 1.0.0 |
|
Number of containers currently in the cluster |
Deprecated since 1.20.0, use |
|
Number of container boot time measured |
Deprecated since 1.20.0, use |
|
Sum of all container boot times and can be used to compute the average boot time |
Deprecated since 1.20.0, use |
|
Container boot times bucket and can be used for alerting when above a threshold; see the Prometheus documentation for more information |
Deprecated since 1.20.0, use |
|
Number of containers per application |
Deprecated since 1.20.0, use |
|
Number of containers per container status |
Deprecated since 1.20.0, use |
|
Number of containers per worker node |
Deprecated since 1.20.0, use |
|
Number of instances currently in the cluster |
Available since 1.20.0 |
|
Number of instance boot time measured |
Available since 1.20.0 |
|
Sum of all instance boot times (can be used to compute the average boot time) |
Available since 1.20.0 |
|
Instance boot times bucket (can be used for alerting when above a threshold; see the Prometheus documentation for more information) |
Available since 1.20.0 |
|
Number of instances per application |
Available since 1.20.0 |
|
Number of instances per instance status |
Available since 1.20.0 |
|
Number of instances per worker node |
Available since 1.20.0 |
|
Total CPUs available in each worker node |
Available since 1.0.0 |
|
Used CPUs in each worker node |
Available since 1.0.0 |
|
Total memory available in each worker node |
Available since 1.0.0 |
|
Used memory in each worker node |
Available since 1.0.0 |
API usage¶
Metrics prefixed with ams_http_
allow to track access to the API.
These metrics are available since Anbox Cloud 1.10.0.
Name |
Description |
---|---|
|
Number of HTTP requests being processed at the moment |
|
The HTTP request latency in seconds |
|
The HTTP request size in bytes |
|
Total number of HTTP requests made |
|
The HTTP response sizes in bytes |
API handlers¶
To give a more granular approach to monitoring, the AMS API metrics contain handlers that identify the kind of API access.
The AMS API can be accessed through HTTP/HTTPS or a Unix domain socket. Therefore, the API metrics distinguish between http
, https
and unix
. For example:
ams_http_request_duration_seconds_bucket{handler="http_applications_GET",host="juju-2db13b-1",method="get",le="0.5"} 1
ams_http_request_duration_seconds_bucket{handler="https_applications_GET",host="juju-2db13b-1",method="get",le="0.5"} 1
ams_http_request_duration_seconds_bucket{handler="unix_applications_GET",host="juju-2db13b-1",method="get",le="0.5"} 1
All handler labels adopt the convention <transport method>_<object>_<http method>
, for example, unix_containers_POST
.
The following table contains all routes and their corresponding labels (ignoring the communication method prefix).
Method |
Route |
Label |
---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Anbox Stream Gateway¶
The Anbox Stream Gateway provides metrics about the streaming activities of your cluster or server and the Anbox Stream Gateway API access.
Objects¶
Metrics prefixed with anbox_stream_gateway_
give information about your cluster related to streaming, for example, the number of sessions and agents.
These metrics are available since Anbox Cloud 1.7.2.
Name |
Description |
---|---|
|
Total number of sessions, categorized by status |
|
Total number of accounts |
|
Number of active agents |
|
Number of unresponsive agents |
API usage¶
Metrics prefixed with anbox_stream_gateway_http_
allow to track access to the streaming API.
These metrics are available since Anbox Cloud 1.9.0.
Name |
Description |
---|---|
|
Number of HTTP requests being processed at the moment |
|
The HTTP request latency in seconds |
|
The HTTP request size in bytes |
|
Total number of HTTP requests made |
|
The HTTP response sizes in bytes |
API handlers¶
To give a more granular approach to monitoring, the Anbox Stream Gateway API metrics contain handlers that identify the route that is accessed. The routes are indicated in the handler labels. For example:
anbox_stream_gateway_http_request_duration_seconds_bucket{handler="get_sessions",host="juju-2db13b-1",method="get",le="0.5"} 1
In this case, the label for the route is get_sessions
.
The following table contains all routes and their corresponding labels.
Method |
Route |
Label |
---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Anbox Runtime metrics¶
For every instance running inside Anbox Cloud, the Anbox runtime provides a set of metrics.
Graphics¶
Name |
Type |
Description |
---|---|---|
|
Counter |
Total number of buffer allocations |
|
Counter |
Total memory in bytes allocated for graphics buffers through Vulkan |
|
Counter |
Total memory in bytes allocated for graphics buffers from system memory |
|
Histogram |
Latency in ms of frames processed by the frame renderer since were submitted |
|
Histogram |
Number of packets per encoded frame |
|
Histogram |
Number of bytes per encoded frame |
WebRTC¶
Metrics prefixed with webrtc_
give you detailed insight about the WebRTC protocol for every streaming instance. See the official W3C reference for more information.
These metrics are available since Anbox Cloud 1.8.0.
Name |
Description |
---|---|
|
Total number of frames successfully encoded |
|
Total number of key frames, such as key frames in VP8 or IDR-frames in H.264 ( |
|
Total number of seconds that has been spent encoding the |
|
The current encoder target in bits per second |
|
Total number of bytes sent for a specific SSRC (a SSRC represents one resource - video, audio or binary data - sent over a WebRTC track) |
|
Total number of bytes that were re-transmitted for a specific SSRC, only including payload bytes |
|
Total number of packets that were re-transmitted for a specific SSRC |
|
Total number of seconds that packets have spent buffered locally before being transmitted onto the network |
|
Total number of RTP packets sent for this SSRC (includes re-transmissions) |
|
Total number of Negative Acknowledgment (NACK) packets received by this sender |
|
Total number of Full Intra Request (FIR) packets received by this sender (video only) |
|
Total number of Picture Loss Indication (PLI) packets received by this sender (video only) |
|
Total number of Slice Loss Indication (SLI) packets received by this sender (video only) |
|
Boolean value indicating if a relay ICE candidate type is in use for the stream |