Collector Configuration Manual for "Alibaba Cloud-RocketMQ 4.0"
Before reading this article, please read the following first:
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: 'cn-hangzhou' Refer to the appendix for the complete list |
2. Configuration Example
Specifying Regions
Collect data from Hangzhou and Shanghai regions.
Python | |
---|---|
1 2 3 |
|
3. Data Reporting Format
After data synchronization is successful, you can view the data in the "Infrastructure - Resource Catalog" section of {{( brand_name }}}.
The reported data format is shown below:
JSON | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
|
Descriptions of some parameters are provided below:
InstanceStatus (Instance Status)
Value | Description |
---|---|
0 |
Platinum edition instance deploying |
2 |
Standard edition instance overdue |
5 |
Standard or platinum edition instance in service |
7 |
Platinum edition instance upgrading with service available |
spInstanceType (Instance Sales Type)
Value | Description |
---|---|
1 |
Standard edition (pay-as-you-go) instance |
2 |
Platinum edition (annual/monthly subscription) instance |
Fields in tags and fields may change with subsequent updates.
The value of tags.name is the instance ID, which serves as a unique identifier.
fields.message, fields.disks, fields.network_interfaces, fields.instance_renew_attribute, fields.instances_full_status, fields.OperationLocks are all JSON-serialized strings.
X. Appendix
Please refer to the official Alibaba Cloud documentation: