Collector Configuration Manual for "Tencent Cloud-RabbitMQ"
Before reading this article, please first read:
Before using this collector, you must install the 'Integration Core Package' and its associated third-party dependency packages
1. Configuration Structure
The configuration structure of this collector is as follows:
Field | Type | Required | Description |
---|---|---|---|
regions |
list | Required | List of regions to collect data from |
regions[#] |
str | Required | Region ID. For example: 'ap-shanghai' Refer to the appendix for the full list |
2. Configuration Example
Specifying Regions
Collect data from Shanghai and Guangzhou regions.
Python | |
---|---|
1 2 3 |
|
3. Data Reporting Format
After the data synchronizes successfully, it can be viewed in the {{( brand_name )}} "Infrastructure - Resource Catalog".
An example of the reported data is as follows:
JSON | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 |
|
Descriptions of some parameters are as follows:
Field | Type | Description |
---|---|---|
Status |
str | Instance status, 0 means creating, 1 means normal, 2 means isolated, 3 means destroyed, 4 - abnormal, 5 - shipping failed |
PayMode |
str | 0 - postpaid, 1 - prepaid |
InstanceVersion |
str | Instance version Note: This field may return null, indicating that a valid value cannot be obtained. |
MaxBandWidth |
str | Peak bandwidth, Mbps as unit |
MaxStorage |
str | Storage capacity, GB as unit |
ExpireTime |
str | Instance expiration time, milliseconds as unit |
ClusterStatus |
str | Instance status, 0 means creating, 1 means normal, 2 means isolated, 3 means destroyed, 4 - abnormal, 5 - shipping failed. To distinguish from billing, an additional status bit is opened for display. |
Fields in tags and fields may change with subsequent updates
The value of tags.name is the instance ID, used as a unique identifier. fields.message is a string serialized in JSON format.
X. Appendix
Please refer to the official Tencent Cloud documentation: