Configuration Manual for Collector 「Tencent Cloud-EIP」
Before reading this, please first read:
Before using this collector, the installation of the 「Core Integration Package」 and its associated third-party dependency packages is required
1. Configuration Structure
The configuration structure for this collector is as follows:
Field | Type | Required | Description |
---|---|---|---|
regions |
list | Required | List of regions to be collected |
regions[#] |
str | Required | Region ID. For example: 'ap-shanghai' See appendix for the complete list |
2. Configuration Example
Specifying Regions
Collect data from Shanghai and Guangzhou regions
Python | |
---|---|
1 2 3 |
|
Configuring Filters (Optional)
This collector script supports user-defined filters, allowing users to filter target resources by object properties. The filter function returns True or False.
- True: Target resource needs to be collected.
- False: Target resource does not need to be collected.
Supported object properties for filtering:
Property | Description |
---|---|
AddressId |
EIP's ID |
AddressName |
EIP Name |
AddressStatus |
EIP Status |
AddressIp |
External IP address |
AddressType |
Instance name |
InternetServiceProvider |
Carrier information for Elastic Public IP |
InternetChargeType |
Network billing mode for Elastic Public IP |
Python | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
|
3. Data Reporting Format
After data synchronization is successful, you can view the data in the 「Infrastructure - Resource Catalog」 section of {{( brand_name }}}.
Example of reported data:
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 28 |
|
Fields in tags and fields may change with subsequent updates
tags.name value is the instance ID, used as a unique identifier
fields.message and fields.EipAlgType are both strings after JSON serialization
X. Appendix
Refer to the official Tencent Cloud documentation: