Message Queue (MQ) Config Guide
Learn how to configure the message queue (RabbitMQ/Azure Service Bus) responsible for asynchronous communication between the GIIP platform and agents.
📋 Overview
The Message Queue (MQ) is the core pathway for reliably delivering massive amounts of data collected by agents to the backend and asynchronously transmitting user commands back to those agents. Proper MQ configuration ensures system responsiveness and data integrity.
🔍 Key Configuration Items
1. Connection Strings
- Host Address: Enter the IP or DNS address of the MQ server.
- Auth Info: Store the username, password, or Shared Access Key encrypted.
2. Queue & Topic Management
- Inbound Queue: The path where metrics/issue data transmitted from agents is accumulated.
- Outbound Queue: The path where administrator commands (
execCommand) are delivered to agents. - DLQ (Dead Letter Queue): A repository where failed messages are isolated, used for failure analysis.
3. Message Retention & Retry Policies
- TTL (Time To Live): Sets the maximum time a message can stay in the queue.
- Retry Count: Defines the maximum number of times to retry a failed message. (Default: 3)
🛠️ Setup Steps
- Navigate to the GIIP [System Management] > [MQ Config] menu.
- Click the [Edit Configuration] button and select your MQ engine type.
- Enter the provided connection string and click [Test Connection] to verify normal operation.
- Once settings are saved, the backend and agent brokers will automatically restart.
💡 Tips
- Load Balancing: Prevent bottlenecks in large-scale infrastructure environments by separating queues with high traffic.
- Monitoring Integration: It is recommended to set up alerts for administrators when the number of messages in the queue (Message Depth) spikes.
API Reference
For detailed API specifications of this feature, refer to the separate guide.
Troubleshooting
| Symptom | Cause | Solution |
|---|---|---|
| [Test Connection] fails | Incorrect Host Address or auth info | Re-check the connection string and auth info, then re-enter them |
| Messages keep piling up in the queue (Message Depth spikes) | Processing delay or consumer bottleneck | Separate high-traffic queues and set up monitoring alerts |
| Failed messages appear to disappear | Moved to the DLQ after exceeding the Retry Count | Check the isolated messages in the DLQ (Dead Letter Queue) to analyze the failure |
| Communication is briefly interrupted right after saving settings | Automatic restart of the backend and agent brokers | Wait until the restart completes (expected behavior) |
Version: 1.0
Last Updated: 2026-03-19
Source: giipv3/public/help/mq-config.en.md