The Cloud Monitor module of TencentCloud Managed Service for Prometheus (TMP) integrates the basic monitoring data of Tencent Cloud products, and implements unified collection, storage, and visualization through TMP.
Note:
Data collection interval: 1 minute. Currently, smaller collection intervals are not supported.
Monitoring data granularity: 1 minute. If a metric does not support the 1-minute granularity, you can select the 5-minute granularity.
The integrated monitoring data includes tag data (not supported by some cloud products) of cloud products. The tag key should conform to the regular expression [a-Za-Z_][a-Za-Z0-9_]*. Otherwise, it will be filtered out.
Multi-region is not supported. If cloud products are distributed in multiple regions, multiple integration modules need to be installed.
2. Select the corresponding Prometheus instance from the instance list.
3. Enter the instance details page, click Data Collection > Integration Center.
4. On the Integration Center page, locate and click Cloud Monitor. On the displayed installation page, define the integration module name, configure the Exporter, and select the corresponding cloud product.
Configuration Instructions
Parameter
Description
name
Exporter name, which should meet the following requirements:
The name should be unique.
The name should conform to the following regular expression: '^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$'.
Region
Required. Region where the cloud product is located. If the cloud product does not distinguish regions, enter any region.
Data Collection Latency
Unit: second. If it is set to 0, the timestamp of the original data will be ignored. If it is set to a value greater than 0, the timestamp of the original data will be reported. Since there is a certain delay in reporting cloud product monitoring data to basic monitoring, this delay will be reflected in the latest data.
Data pulling range: (Current time - Data collection delay - Fixed interval, Current time - Data collection delay).
Instance Refresh Interval
Unit: minute. The minimum value is 10. At each instance refresh interval, the integration module will re-pull cloud product instance information. If the instance name or cloud tag is modified or an instance is added or deleted, the monitoring data will be updated within one instance refresh interval.
Instance ID Filtering
Optional. If it is left blank, data will be collected from all instances under the root account by default. Enter a value in the form of the key-value pair, where the key is the unique ID of the cloud product defined by the integration module, and the value is a list of comma-separated cloud product instance IDs. Only data of the instances of the cloud products specified in the key-value pair form will be collected.
Cloud Tag Key Filtering
Optional. Enter a value in the form of the key-value pair, where one tag key can correspond to multiple tag values that are separated by |. Take the intersection of different tag keys and take the union of multiple tag values under the same tag key. For products that support cloud tag filtering, if instance ID filtering is also configured, cloud tag filtering for that product will not take effect.
Cloud Tag Key Replacement
Optional. Replace illegal cloud product tag keys with valid values. For example, convert Chinese names into custom English names.
Cloud Tag Key Operations
By default, the integration module converts uppercase letters in tag keys into underscores followed by lowercase letters. It supports the conversion of tag keys of cloud products.
ToUnderLineAndLower: default operation.
ToLower: full conversion to lowercase letters.
NoOperation: no conversion.
Label
Optional. You can add additional custom tags to the metrics collected by the integration module.
Tencent Cloud Products
Select the cloud product you want to collect.
Metric Relabel
Optional. Native metricRelabelings configuration for Prometheus Operator. The configuration method is the same as metric_relabel_configs in Prometheus scraping configuration, with only some field naming conventions being different.
Metric Relabel Configuration Examples
The common metricRelabelings examples are as follows:
metricRelabelings:
-action: labeldrop # Remove the label named labelA. regex indicates a regular expression, and multiple expressions are separated by |.
regex: labelA
-regex: ins-(.*)# Add a label named id, whose value is derived from the value of the label instance_id after a regular expression is applied. For example, if the value of instance_id is ins-a, the value of id is a.
replacement: $1
sourceLabels:
- instance_id
targetLabel: id
-targetLabel: region # Add a label with region being ap-guangzhou.
replacement: ap-guangzhou
-action: drop # Remove the metric named metricA or metricB.
By default, metrics at the instance dimension are collected. If metrics at the listener, forwarding rule domain name, or backend server dimension are required, submit a ticket. The names of metrics at different dimensions are the same name, which can be distinguished by the monitor_view tag.
By default, metrics at the instance dimension are collected. If metrics at the listener or forwarding rule domain name dimension are required, submit a ticket. The names of metrics at different dimensions are the same name, which can be distinguished by the monitor_view tag.
Storage-related metrics have a high delay (about 2 hours), and the original timestamp of the data is not retained. Storage-related metrics do not support the 1-minute granularity. By default, 5-minute data is pulled.
They are the same as the VPC, network connection, and DC gateway.
Lighthouse
Yes
Lighthouse
-
Cloud-native API gateway
Yes
apigw_cloudnative
By default, metrics at the instance and public network CLB dimensions are collected. If metrics at the node dimension are required, submit a ticket. The names of metrics at the instance and node dimensions are the same name, which can be distinguished by the monitor_view tag.
By default, metrics at the alias dimension are collected. If metrics at the version dimension are required, submit a ticket. The names of metrics at the alias and version dimensions are the same name, which can be distinguished by the monitor_view tag.
The Prometheus instance has been bound to a Grafana instance.
Operation Steps
1. Log in to the TMP console and select the corresponding Prometheus instance to enter its management page.
2. Click Data Collection > Integration Center, on the Integration Center page, find and click Cloud Monitor, select Dashboard > Dashboard operation > Install/Upgrade in the pop-up window to install the corresponding Grafana Dashboard.
3. Select Integrated. In the integrated list, click the Grafana icon to automatically open the list of Cloud Monitor integrated dashboards. Select the corresponding cloud product dashboard to view monitoring data related to the instance, as shown below.
Yes
No
Was this page helpful?