HiveMQ Cloud Metrics
Metrics Index
Metric | Type | Description |
---|---|---|
|
|
Counts every closed connection that was closed because the client missed sending a PINGREQ message during the keep-alive interval |
|
|
The current number of queued messages for client sessions |
|
|
The current number of pending QoS 0 messages for client sessions |
|
|
The total number of pending messages for client sessions |
|
|
The number of PUBLISH messages that dropped because the message queue for a consumer topic was full |
|
|
The total number of dropped messages on the broker |
|
|
The number of PUBLISH messages that dropped because a Publish Inbound Interceptor prevented onward delivery |
|
|
The number of PUBLISH messages that dropped because of an internal error |
|
|
The number of PUBLISH messages that dropped because the message size was too large for the client |
|
|
The number of MQTT messages (excluding PUBLISH packets) that dropped because the message size was too large for the client |
|
|
The number of PUBLISH messages that dropped because the socket for the client was not writable (QoS 0 only) |
|
|
The number of PUBLISH messages that dropped because a policy prevented onward delivery |
|
|
The number of PUBLISH messages that dropped because the global memory limit for QoS 0 messages was exceeded |
|
|
The number of PUBLISH messages that dropped because the message queue for a disconnected persistent session client was full |
|
|
The number of PUBLISH messages that are dropped because the message queue for a shared subscription is full |
|
|
The total number of expired messages on the broker |
|
|
Counts every incoming MQTT CONNECT message |
|
|
Counts every incoming MQTT PUBLISH message |
|
|
Counts every outgoing MQTT PUBLISH message |
|
|
The current total number of active MQTT connections |
|
|
Counts the amount of publish messages received, without any matching subscribers |
|
|
The current number of stored sessions. These sessions include all sessions, including online and offline clients |
|
|
The current number of active persistent sessions (= Online MQTT clients which are connected with cleanSession=false) |
|
|
The current number of subscriptions on the broker |
|
|
The current number of shared subscriptions on the broker |
|
|
Total number of normalized messages |
|
|
The total number of records the extension cannot produce to Kafka. |
|
|
The total number of records the extension ignored. |
|
|
The total number of records that were retried to be produced to Kafka. |
|
|
The total number of records the extension attempts to send to Kafka. |
|
|
The total number of records the extension successfully produced to Kafka. |
|
|
The total number of messages the extension drops from MQTT to Google Cloud Pub/Sub. |
|
|
The total number of MQTT to Google Cloud Pub/Sub messages the extension cannot successfully forward. |
|
|
The total number of MQTT to Google Cloud Pub/Sub messages the extension ignores. |
|
|
The total number of MQTT to Google Cloud Pub/Sub messages the extension resends. |
|
|
The total number of MQTT to Google Cloud Pub/Sub messages the extension sends. |
|
|
The total number of MQTT to Google Cloud Pub/Sub messages from all transformers and mappings that the extension successfully forwards. |
|
|
Incoming messages per extension |
|
|
Outgoing messages per extension |
|
|
The number of connected clients to which at least one non-terminated behavior currently applies |
|
|
The total number of failed terminations of behaviors |
|
|
The total number of successful terminations of behaviors |
|
Customer metrics that support IncrementBy semantics |
OpenAPI Reference
For a detailed API reference, see: OpenAPI
Access HiveMQ Broker Metrics From a Remote Service
To retrieve raw metrics from a service, follow these steps:
Generate an API Token
-
Log into the HiveMQ Cloud web console, navigate to API Access in the top navigation of your HiveMQ Cloud cluster, and select Create API token.
-
On the Create API Token page, enter a unique name for the new token in the Token name field and select Custom in the Access Type field.

-
In the Access Type field select Custom.
-
From the Custom permissions options, select the Read and Otel metrics custom permissions.

-
To create the new API token, select Create API token.
-
On the API Access overview, select Copy Token. NOTE: Make sure to copy your token. Once you leave the API page, you will be unable to copy the token.
Make an API Call
-
Retrieve your broker metrics in your own environment by running the following command:
curl -v https://${YOUR_REST_API_BASE_URL}/metrics -H "Authorization: Bearer ${TOKEN}"
-
YOUR_REST_API_BASE_URL
: From the API Access tab. -
TOKEN
: The API token you generated and copied in the previous steps.
Integrating HiveMQ Broker Metrics into Prometheus
To collect and monitor HiveMQ Cloud metrics in Prometheus, follow these steps:
-
Edit your Prometheus configuration (
prometheus.yml
) -
Add the following scrape job:
scrape_configs:
- job_name: 'hivemq'
metrics_path: /metrics
scheme: https
static_configs:
- targets:
- "https://${YOUR_REST_API_BASE_URL}/metrics"
authorization:
credentials: "Bearer ${TOKEN}"
Replace |