You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 22, 2026. It is now read-only.
Copy file name to clipboardExpand all lines: _includes/docs/mqtt-broker/user-guide/ui/monitoring.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
4
4
TBMQ offers user-friendly tools that enable users to monitor broker activity and conveniently access features through the **Home** and **Monitoring** pages.
@@ -30,7 +30,7 @@ Users can access comprehensive information about these sessions, including their
30
30
The system displays the number of Client Credentials categorized into two types: **Device** and **Application**.
31
31
For more information regarding the different types of Credentials, please refer to the [documentation](/docs/mqtt-broker/user-guide/mqtt-client-type/).
@@ -52,15 +52,15 @@ Contains information regarding some commonly used configuration parameters:
52
52
-**WS Listener Max Payload Size.** Specifies the maximum allowed size of the payload in a WS message. The default value is `65536` bytes. To modify it, set the `WS_NETTY_MAX_PAYLOAD_SIZE` environment variable in bytes.
53
53
-**WSS Listener Max Payload Size.** Defines the maximum allowed size of the payload in a WSS-encrypted message. The default value is `65536` bytes. To change it, set the `WSS_NETTY_MAX_PAYLOAD_SIZE` environment variable in bytes.
@@ -80,7 +80,7 @@ Displays basic information regarding the Kafka Consumer Groups (CG):
80
80
-**Members.** Number of consumers in the CG.
81
81
-**Lag.** Sum of all consumers lags within the group. Consumer lag is the delta between the consumer's last committed offset and the producer's end offset.
@@ -117,4 +117,4 @@ Services are automatically added to the registry on their first launch, and the
117
117
The key is not managed by TTL and entries are stored indefinitely. TBMQ does not automatically remove services from the registry, even if they stop running.
118
118
You can manually delete a service from the UI (or using REST API) using the "Delete" button that is available only when the service status is `Outdated`.
title: 'After adding the credentials, the "Check Connectivity" window will open. This window includes autogenerated commands for subscribing to a topic or publishing a message.'
title: 'Select the verification type that matches how your tokens are issued. If unsure, HMAC-based is usually the easiest to start with during testing.'
title: 'Add a custom HTTP header to JWKS requests. This example shows the Content-Type: application/json header and a placeholder for an additional custom header.'
title: 'Client type is set to "DEVICE" by default. If the JWT contains claim "role" with the value "app", the client will be classified as "APPLICATION".'
title: 'The JWT claim "pub_rules" restricts publish access to "devices/.*/data", while claim "sub_rules" expands subscribe access to include "alerts/.*".'
0 commit comments