Collector Configuration Manual for "Tencent Cloud - SQL Server"
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' See appendix for full list |
2. Configuration Example
Specify Region
Collect data from Shanghai region
Python | |
---|---|
1 2 3 |
|
Configure Filters (Optional)
This collector script supports user-defined filters that allow users to filter target resources by 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 |
---|---|
DBInstanceId | Instance ID |
AppId | User's AppId |
DBCharset | Database character set |
DBEngine | Database engine |
DBInstanceClass | Instance type |
DBInstanceName | Instance name |
ProjectId | Project ID |
Region | Project ID where the instance resides |
Type | Machine type |
SubnetId | Subnet ID |
PayType | Payment type |
Python | |
---|---|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
|
3. Data Reporting Format
After data synchronization is successful, 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 28 29 30 31 32 33 34 35 36 |
|
Fields in tags and fields may change with subsequent updates
tags.name value is a unique identifier
fields.message and fields.InstanceNode are JSON serialized strings
X. Appendix
Refer to the official Tencent Cloud documentation: