Collector Configuration Manual for "Volcengine-RabbitMQ"
Before reading this article, please read the following first:
Before using this collector, you must install the 'Core Integration 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-shanghai' Refer to the appendix for the full list |
2. Configuration Example
Specifying Regions
Collecting data from the Beijing region.
Python | |
---|---|
1 2 3 |
|
Configuring Filters (Optional)
This collector script supports user-defined filters, allowing users to filter target resources based on object properties. The filter function returns True or False.
- True: The target resource needs to be collected.
- False: The target resource does not need to be collected.
Supported object properties for filtering:
Property | Description |
---|---|
InstanceId | Instance ID |
InstanceName | Instance Name |
InstanceStatus | Instance Status |
ZoneId | Availability Zone ID |
ProjectName | Project Name |
Version | RabbitMQ Version |
VpcId | Private Network ID |
Python | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
|
3. Data Reporting Format
After data synchronization, you can view the data in the "Infrastructure - Resource Catalog" section of {{( brand_name }}}.
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 23 24 25 26 27 |
|
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 and fields.TagMap are strings serialized in JSON format.
X. Appendix
Please refer to the official Volcengine documentation: