Skip to content

FMQ Manual ​

Documentation Center / Professional Edition / 1.3 FMQ Manual

Operations Manual ​

The documentation keeps the original manual numbering; missing numbers are not filled with fabricated content.

No.DocumentApplicable Tasks
1Monitoring OverviewView cluster health, ingestion rates, event bus, rules, and scheduling resources.
2Link Monitoring DetailsInspect runtime status by link segment and locate the layer where an anomaly occurs.
3Service ManagementView listener service status, configuration, and the boundaries of runtime operations.
4-1MQTT ClientComplete the MQTT device access, uplink, downlink, offline, and recovery loop.
4-2TCP ClientComplete the TCP device access, data send/receive, disconnect, and recovery loop.
5UDP ManagementLocate UDP sessions and verify uplink, downlink, and offline status.
6Protocol ManagementReview the protocol catalog, debug entry, external packages, and authorization boundaries.
7Runtime Configuration CenterManage runtime parameters and determine the scope of saving, activation, rebinding, and recovery.
9Integration: ConnectorsConfigure external connection resources such as RabbitMQ, Kafka, MQTT, and HTTP.
10Integration: Third-party Upstream SourcesIngest external MQTT, HTTP, or Kafka data and verify actual receipt.
11Integration: Message PushConfigure event filtering and push targets, and verify actual receipt on external systems.
12Integration: Command DownlinkDeliver commands to devices from external entries and check command status.
13Tracing: MQTTTrace MQTT device connections, messages, exceptions, and recovery.
14Tracing: TCPTrace TCP device business frames, downlink, retries, and recovery.
15Tracing: Modbus TCPTrace polling, message parsing, pausing, circuit breaking, and recovery.
17MQTT AuthenticationConfigure authentication policies and verify actual connections with MQTTX.
18MQTT SubscriptionsQuery subscription relationships and verify real send/receive with MQTTX.
19MQTT×RabbitMQ×JSON from Zero to OneStarting from resource preparation, complete one JSON uplink report and verify both the RabbitMQ manual branch and the platform main path.

Back to the Documentation Center