Tencent Cloud COS¶
Use the "Guance Cloud Sync" series of script packages in the script market to sync cloud monitoring and cloud asset data to Guance.
Configuration¶
Install Func¶
It is recommended to activate the Guance Integration - Extensions - DataFlux Func (Automata): all prerequisites are automatically installed. Please proceed with the script installation.
If you deploy Func yourself, refer to Self-deploy Func
Activate Script¶
Note: Please prepare the Tencent Cloud AK that meets the requirements in advance (for simplicity, you can directly grant the global read-only permission
ReadOnlyAccess)
Activate Script in DataFlux Func (Automata)¶
- Log in to the Guance console.
- Click the [Integration] menu and select [Cloud Account Management].
- Click [Add Cloud Account], select [Tencent Cloud], and fill in the required information on the interface. If you have already configured the cloud account information before, ignore this step.
- Click [Test], and after the test is successful, click [Save]. If the test fails, please check if the relevant configuration information is correct and test again.
- Click [Cloud Account Management], and you can see the added cloud account in the list. Click the corresponding cloud account to enter the details page.
- Click the [Integration] button on the cloud account details page, find
Tencent Cloud COSunder theNot Installedlist, and click the [Install] button to install it.
Manually Activate Script¶
-
Log in to the Func console, click [Script Market], enter the Guance script market, and search for
integration_tencentcloud_cos. -
Click [Install], then enter the corresponding parameters: Tencent Cloud AK, SK, and account name.
-
Click [Deploy Startup Script], the system will automatically create the
Startupscript set and automatically configure the corresponding startup scripts. -
After enabling, you can see the corresponding automatic trigger configuration in "Management / Automatic Trigger Configuration". Click [Execute] to execute it immediately without waiting for the scheduled time. After a while, you can view the execution task records and corresponding logs.
Verification¶
- In "Management / Automatic Trigger Configuration", confirm whether the corresponding task has the corresponding automatic trigger configuration, and check the corresponding task records and logs for any exceptions.
- In Guance, check if asset information exists in "Infrastructure / Custom".
- In Guance, check if there is corresponding monitoring data in "Metrics".
Metrics¶
After configuring Tencent Cloud COS collection, the default collected measurement is as follows. More metrics can be collected through configuration Tencent Cloud Monitoring Metrics Details
Request Class¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimensions |
|---|---|---|---|---|
| StdReadRequests | Standard Storage Read Requests | Standard storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| StdWriteRequests | Standard Storage Write Requests | Standard storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| MazStdReadRequests | Multi-AZ Standard Storage Read Requests | Multi-AZ standard storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| MazStdWriteRequests | Multi-AZ Standard Storage Write Requests | Multi-AZ standard storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| IaReadRequests | Infrequent Access Storage Read Requests | Infrequent access storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| IaWriteRequests | Infrequent Access Storage Write Requests | Infrequent access storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| MazIaReadRequests | Multi-AZ Infrequent Access Storage Read Requests | Multi-AZ infrequent access storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| MazIaWriteRequests | Multi-AZ Infrequent Access Storage Write Requests | Multi-AZ infrequent access storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| DeepArcReadRequests | Deep Archive Storage Read Requests | Deep archive storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| DeepArcWriteRequests | Deep Archive Storage Write Requests | Deep archive storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| ItReadRequests | Intelligent Tiering Storage Read Requests | Intelligent tiering storage type read request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| ItWriteRequests | Intelligent Tiering Storage Write Requests | Intelligent tiering storage type write request count, request count is calculated based on the number of request commands sent | times | appid, bucket |
| TotalRequests | Total Requests | Total read and write request count for all storage types, request count is calculated based on the number of request commands sent | times | appid, bucket |
| GetRequests | GET Class Total Requests | Total GET class request count for all storage types, request count is calculated based on the number of request commands sent | times | appid, bucket |
| PutRequests | PUT Class Total Requests | Total PUT class request count for all storage types, request count is calculated based on the number of request commands sent | times | appid, bucket |
Storage Class¶
| Metric Name | Metric Chinese Name | Unit | Dimensions |
|---|---|---|---|
| Size | Bucket Storage Capacity | B | Name |
Traffic Class¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimensions |
|---|---|---|---|---|
| InternetTraffic | Internet Downstream Traffic | Traffic generated when data is downloaded from COS to the client via the internet | B | appid, bucket |
| InternetTrafficUp | Internet Upstream Traffic | Traffic generated when data is uploaded from the client to COS via the internet | B | appid, bucket |
| InternalTraffic | Internal Downstream Traffic | Traffic generated when data is downloaded from COS to the client via Tencent Cloud internal network | B | appid, bucket |
| InternalTrafficUp | Internal Upstream Traffic | Traffic generated when data is uploaded from the client to COS via Tencent Cloud internal network | B | appid, bucket |
| CdnOriginTraffic | CDN Origin Traffic | Traffic generated when data is transferred from COS to Tencent Cloud CDN edge nodes | B | appid, bucket |
| InboundTraffic | Total Internet and Internal Upload Traffic | Traffic generated when data is uploaded from the client to COS via the internet and Tencent Cloud internal network | B | appid, bucket |
| CrossRegionReplicationTraffic | Cross-Region Replication Traffic | Traffic generated when data is transferred from a bucket in one region to a bucket in another region | B | appid, bucket |
Response Code Class¶
| Metric Name | Metric Chinese Name | Metric Description | Unit | Dimensions |
|---|---|---|---|---|
| 2xxResponse | 2xx Status Code | Request count with 2xx status code | times | appid, bucket |
| 3xxResponse | 3xx Status Code | Request count with 3xx status code | times | appid, bucket |
| 4xxResponse | 4xx Status Code | Request count with 4xx status code | times | appid, bucket |
| 5xxResponse | 5xx Status Code | Request count with 5xx status code | times | appid, bucket |
| 2xxResponseRate | 2xx Status Code Ratio | Ratio of requests with 2xx status code to total requests | % | appid, bucket |
| 3xxResponseRate | 3xx Status Code Ratio | Ratio of requests with 3xx status code to total requests | % | appid, bucket |
| 4xxResponseRate | 4xx Status Code Ratio | Ratio of requests with 4xx status code to total requests | % | appid, bucket |
| 5xxResponseRate | 5xx Status Code Ratio | Ratio of requests with 5xx status code to total requests | % | appid, bucket |
| 400Response | 400 Status Code | Request count with 400 status code | times | appid, bucket |
| 403Response | 403 Status Code | Request count with 403 status code | times | appid, bucket |
| 404Response | 404 Status Code | Request count with 404 status code | times | appid, bucket |
| 400ResponseRate | 400 Status Code Ratio | Ratio of requests with 400 status code to total requests | % | appid, bucket |
| 403ResponseRate | 403 Status Code Ratio | Ratio of requests with 403 status code to total requests | % | appid, bucket |
| 404ResponseRate | 404 Status Code Ratio | Ratio of requests with 404 status code to total requests | % | appid, bucket |
| 500ResponseRate | 500 Status Code Ratio | Ratio of requests with 500 status code to total requests | % | appid, bucket |
| 501ResponseRate | 501 Status Code Ratio | Ratio of requests with 501 status code to total requests | % | appid, bucket |
| 502ResponseRate | 502 Status Code Ratio | Ratio of requests with 502 status code to total requests | % | appid, bucket |
| 503ResponseRate | 503 Status Code Ratio | Ratio of requests with 503 status code to total requests | % | appid, bucket |
Objects¶
The collected Tencent Cloud COS object data structure can be seen in "Infrastructure - Custom".