HiveMQ Cloud Metrics
The metrics HiveMQ exposes for your HiveMQ Cloud cluster vary based on your HiveMQ Cloud plan.
Currently, metrics are exposed for HiveMQ Cloud Enterprise plan clusters, only. |
Available Metrics - HiveMQ Cloud Enterprise Plan
The following HiveMQ metrics are available for all HiveMQ Cloud Enterprise clusters:
Metric | Type | Description |
---|---|---|
|
|
Counts every closed connection that was closed because the client missed sending 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 total number of dead messages the broker detects |
|
|
The number of $dead messages that are queued to a $dead topic |
|
|
The number of $dead messages that are dead more than once |
|
|
The number of $dead messages that are dropped |
|
|
The number of $dead messages that are expired |
|
|
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 number of $dropped messages that are dead |
|
|
The number of $dropped messages that dropped due to queue limits |
|
|
The number of $dropped messages that originate from clients |
|
|
The number of $dropped messages that originate from shared subscriptions |
|
|
The number $dropped messages that originate from consumers |
|
|
The number of $dropped messages that are enqueued for a $dropped topic |
|
|
The total number of expired messages on the broker |
|
|
The number of $expired messages that are dead |
|
|
The number of $expired messages that are dropped due to queue limits |
|
|
The number of $expired messages that expire more than once |
|
|
The number of expired messages that are enqueued for an $expired topic |
|
|
Counts every incoming MQTT CONNECT message |
|
|
Counts every incoming MQTT 3 CONNECT message |
|
|
Counts every incoming MQTT 5 CONNECT message |
|
|
Counts every incoming MQTT PUBLISH message |
|
|
Counts every incoming MQTT PUBLISH message that is sent with quality of service (QoS) level 0 |
|
|
Counts every incoming MQTT PUBLISH message that is sent with quality of service (QoS) level 1 |
|
|
Counts every incoming MQTT PUBLISH message that is sent with quality of service (QoS) level 2 |
|
|
Counts every outgoing MQTT PUBLISH message |
|
|
Counts every outgoing MQTT PUBLISH message that is sent with quality of service (QoS) level 0 |
|
|
Counts every outgoing MQTT PUBLISH message that is sent with quality of service (QoS) level 1 |
|
|
Counts every outgoing MQTT PUBLISH message that is sent with quality of service (QoS) level 2 |
|
|
The current number of queued messages |
|
|
The current total number of active MQTT connections |
|
|
Holds the current level of overload protection |
|
|
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 |
|
|
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. |
|
|
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 |
|
|
The current number of policy entries in the behavior policy persistence |
|
|
The total number of failed schema deserializations in behavior policies |
|
|
The total number of successful schema deserializations in behavior policies |
|
|
The total number of behavior states initialized for all clients |
|
|
The mean execution time of the behavior validation in nanoseconds |
|
|
The total number of state transitions behaviors perform |
|
|
The current number of data policy entries in the persistence |
|
|
The total number of payloads that failed to validate successfully |
|
|
The total number of payloads that validated successfully |
|
|
The total number of policies that had a failed outcome |
|
|
The total number of policies that had a successful outcome |
|
|
The total number of validators that had a failed outcome |
|
|
The total number of validators that had a successful outcome |
|
|
The total number of failed schema validations |
|
|
The total number of successful schema validations |
|
|
The mean execution time of publish validation in nanoseconds (including all policy engine iterations) |
|
|
The number of PUBLISH messages that are dropped because a policy prevented onward delivery |
|
|
The current amount of schema entries in the persistence |
|
|
The current number of loaded scripts in the script engine |
|
|
Measures the current rate of scripts executed in script engines |
|
|
The mean execution time of scripts executed in script engines in nanoseconds |
|
|
The current number of bytes allocated for the heap per script engine on average |
|
|
The current number of bytes used for the heap per script engine on average |
|
|
The absolute limit in bytes for the heap that a script engine cannot exceed |
|
|
The current number of script entries in the persistence |
|
Customer metrics that support IncrementBy semantics |