Data Health
Data Health shows how well your live MQTT traffic matches the namespace definitions you created in Contextualize. Use the Data Health in Total metrics to assess traffic quality across your connected brokers. Use the Data Health per Broker panel to identify the brokers that report deviating traffic.
| The Analyze view has two tabs: Data Health and Deviations. This page describes the Data Health tab. For the Deviations tab, see Review Deviations. |
| Set the optional timeframe selector to limit the metrics shown on the page to a specific period. For example, Last Week. |
How the HiveMQ Platform Categorizes Traffic
The broker uses the namespace definition and the state of each topic to assign traffic to one of four categories:
-
Governed traffic: Traffic on topics that match an active namespace node. The broker validates each payload against the node definition and reports any deviations.
-
Ungoverned traffic: Traffic on topics that do not match any namespace node. Discovery collects samples from these topics so that you can review them.
-
Ignored traffic: Traffic on topics that you explicitly mark as ignored in Discovery. The broker does not apply governance to these topics.
-
Inactive node traffic: Traffic on topics that match an inactive namespace node. The broker does not validate these payloads and does not add these topics to Discovery.
Governed Traffic
├── Healthy Traffic
└── Deviating TrafficDeviating Traffic counts governed messages with at least one deviation that you have not ignored. Healthy Traffic equals the governed message count minus the deviating message count. An ignored deviation rule suppresses a reported issue on a governed node. The topic remains governed and does not become an ignored topic. If you ignore all deviations on a message, the message counts as healthy traffic.
Total Traffic includes messages for inactive nodes. The page does not show a separate metric for inactive node traffic. As a result, governed traffic and ungoverned traffic do not add up to the total traffic.
Data Health in Total
The Data Health in Total panel summarizes the quality of all traffic across your connected brokers for the selected timeframe. Each metric shows its share, the number of messages, and the trend over the timeframe.
| Metric | Description |
|---|---|
Total Traffic |
All messages observed across your connected brokers in the selected timeframe. |
Governed Traffic |
Traffic that belongs to active nodes in your Unified Namespace. |
Ungoverned Traffic |
The share of traffic that is not part of the namespace. Use Discover Data Streams in Contextualize to bring ungoverned traffic under governance. |
Healthy Traffic |
The governed message count minus the deviating message count. This count includes messages whose deviations are all ignored. |
Deviating Traffic |
Governed messages with at least one deviation that you have not ignored. To inspect each deviation, see Review Deviations. |
Ignored Traffic |
Traffic on topics you have explicitly chosen to ignore. |
Data Health per Broker
The Data Health per Broker panel shows traffic metrics and the connection state of each broker that supports governance. To find a specific broker, enter its name or ID in the search field.
| Column | Description |
|---|---|
Name |
The name of the broker, such as |
Type |
The broker type, such as Edge or Enterprise. |
State |
The connection state, such as Connected. |
Healthy |
The healthy message count and the change in its share compared with the previous period. |
Deviating |
The deviating message count and the change in its share compared with the previous period. |
Ratio |
The proportion of healthy to deviating traffic on the broker. |
Deviations over Timeframe |
The trend of deviations on the broker during the selected timeframe. |
Actions |
Open the Deviations tab for the broker. |