Skip to main content
Version: Next (Incubating)

Tenant-level Metrics

Below is a comprehensive table of BifroMQ's tenant metrics, including their MetricName (as recognized within Micrometer), the type of meter used, and a brief description of each metric's purpose. It's important to note that the final naming convention of metrics as stored in the collection backend may vary depending on the specific collector used. For detailed mapping relationships, refer to the official Micrometer documentation.

Metric NameMeter TypeDescription
mqtt.connection.num.gaugeGAUGECurrent number of MQTT connections.
mqtt.auth.failure.countCOUNTERthe counter of authentication failures.
mqtt.connect.countCOUNTERThe counter of MQTT connect.
mqtt.disconnect.countCOUNTERthe counter of MQTT disconnect.
mqtt.session.mem.gaugeGAUGEMemory usage by MQTT sessions.
mqtt.psession.space.gaugeGAUGEStorage space used by persistent MQTT sessions.
mqtt.psession.live.num.gaugeGAUGENumber of live persistent MQTT sessions.
mqtt.psession.num.gaugeGAUGETotal number of persistent MQTT sessions.
mqtt.ingress.bytesDISTRIBUTION_SUMMARYBytes received by the broker.
mqtt.egress.bytesDISTRIBUTION_SUMMARYBytes sent from the broker.
mqtt.channel.latencyTIMERLatency of network channels.
mqtt.ingress.qos0.bytesDISTRIBUTION_SUMMARYBytes received for QoS 0 messages.
mqtt.qos0.dist.bytesDISTRIBUTION_SUMMARYDistribution of QoS 0 message bytes.
mqtt.ingress.qos1.bytesDISTRIBUTION_SUMMARYBytes received for QoS 1 messages.
mqtt.qos1.dist.bytesDISTRIBUTION_SUMMARYDistribution of QoS 1 message bytes.
mqtt.ingress.qos2.bytesDISTRIBUTION_SUMMARYBytes received for QoS 2 messages.
mqtt.qos2.dist.bytesDISTRIBUTION_SUMMARYDistribution of QoS 2 message bytes.
mqtt.egress.qos0.bytesDISTRIBUTION_SUMMARYBytes sent from broker for QoS 0 messages.
mqtt.egress.qos1.bytesDISTRIBUTION_SUMMARYBytes sent from broker for QoS 1 messages.
mqtt.deliver.qos1.bytesDISTRIBUTION_SUMMARYBytes delivered for QoS 1 messages.
mqtt.egress.qos2.bytesDISTRIBUTION_SUMMARYBytes sent from broker for QoS 2 messages.
mqtt.deliver.qos2.bytesDISTRIBUTION_SUMMARYBytes delivered for QoS 2 messages.
mqtt.in.qos0.latencyTIMERInternal latency for QoS 0 message processing.
mqtt.in.qos1.latencyTIMERInternal latency for QoS 1 message processing.
mqtt.ex.qos1.latencyTIMERExternal latency for QoS 1 message delivery.
mqtt.in.qos2.latencyTIMERInternal latency for QoS 2 message processing.
mqtt.ex.qos2.latencyTIMERExternal latency for QoS 2 message delivery.
mqtt.tfanout.bytesDISTRIBUTION_SUMMARYBytes fanned out for transient messages.
mqtt.pfanout.bytesDISTRIBUTION_SUMMARYBytes fanned out for persistent messages.
mqtt.route.space.gaugeGAUGESpace used for message routing.
mqtt.shared.sub.num.gaugeGAUGENumber of shared subscriptions.
mqtt.tsub.countCOUNTERCount of transient subscriptions.
mqtt.tsub.latencyTIMERLatency in handling transient subscriptions.
mqtt.psub.countCOUNTERCount of persistent subscriptions.
mqtt.psub.latencyTIMERLatency in handling persistent subscriptions.
mqtt.tunsub.countCOUNTERCount of transient unsubscriptions.
mqtt.tunsub.latencyTIMERLatency in handling transient unsubscriptions.
mqtt.punsub.countCOUNTERCount of persistent unsubscriptions.
mqtt.punsub.latencyTIMERLatency in handling persistent unsubscriptions.
mqtt.tsub.num.gaugeGAUGENumber of transient subscriptions currently active.
mqtt.psub.num.gaugeGAUGENumber of persistent subscriptions currently active.
mqtt.ingress.retain.bytesDISTRIBUTION_SUMMARYBytes received for retained messages.
mqtt.retained.bytesDISTRIBUTION_SUMMARYTotal bytes of retained messages stored.
mqtt.retained.num.gaugeGAUGENumber of retained messages stored.
mqtt.retain.match.countCOUNTERCount of retained message matches.
mqtt.retain.matched.bytesDISTRIBUTION_SUMMARYBytes of retained messages delivered after matching.
mqtt.retain.space.gaugeGAUGESpace used for storing retained messages.
  • Internal latency measures the time between the broker receiving a message and the broker sending the message to subscribing clients.
  • External latency measures the time between the broker sending the message to subscribing clients and the broker got the acknowledgement from clients, so it's only applied to QoS1 messages(when PubAck received) and QoS2 messages(when PubComp received).