Release Notes
Connecting to Prometheus for External Monitoring
Scenarios
TDMQ for MQTT has integrated with the TencentCloud Managed Service for Prometheus (TMP) - Cloud Monitor module on Tencent Cloud Observability Platform (TCOP). This module integrates fundamental monitoring capabilities of cloud products. TMP ensures unified data collection, storage, and visualized display, enabling more automated online Ops.
Operation Steps
Step 1: Creating a TDMQ for MQTT Cluster Instance
1. Log in to the TDMQ for MQTT console.
2. In the left sidebar, choose Cluster > Cluster List, and click Create Cluster at the top-left corner to go to the purchase page.
3. On the purchase page, select the region, availability zone (AZ), cluster type and model, cluster specifications, and other information. For detailed parameter descriptions, see Creating a Cluster.
4. After the information is specified, click Buy Now, wait for the cluster to be created, and record the cluster ID for subsequent use in the TMP monitoring data collection configuration.
Step 2: Collecting Monitoring Data with Prometheus
1. Log in to TCOP and select TMP. If no TMP instance exists, click Create to create one. For detailed instructions, see Creating a TMP Instance.
Note:
When a TMP instance is created, ensure that the bound virtual private cloud (VPC) network and subnet are consistent with the vpcId and subnetId in Step 1. Otherwise, network connectivity issues occur.
2. In the instance list, click a TMP instance to go to the instance details page. Choose Data Collection > Integration Center, locate Cloud Monitor in Monitoring, and click it to go to the details page.
3. In the pop-up window, enter the basic information and select a region. Choose TDMQ for MQTT for Cloud Product.
The following table describes parameter configurations.
Parameter | Description |
Name | Integration name, which should comply with the following naming conventions: 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 | Region where the TDMQ for MQTT instance to be collected is located. It is required. |
Data Pulling Configuration | Unit: second. If it is set to 0, the timestamp of the original data is ignored. If it is set to a value greater than 0, the timestamp of the original data is reported. Since there is a certain delay in reporting monitoring data to the Basic Monitoring module, this delay is 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 re-pulls instance information. If the instance name or cloud tag is modified or an instance is added or deleted, the monitoring data is updated within one instance refresh interval. |
Instance ID Filtering | Optional. If it is left blank, data is collected from all instances under the root account by default. A key-value pair indicates that only the specified instances will be collected. Enter a key-value pair, where the key is TDMQ for MQTT, and the value is a list of comma-separated MQTT instance IDs that you want to monitor. |
Cloud Tag Filtering | Optional. Enter a key-value pair, where one tag key can correspond to multiple tag values that are separated by vertical bars (|). 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. It is used to replace invalid tag keys with valid values. For example, it can convert Chinese names to custom English names. |
Cloud Tag Key Operation | By default, the integration module converts uppercase letters in tag keys into underscores followed by lowercase letters. It supports the conversion of tag keys. ToUnderLineAndLower: default operation. ToLower: indicates converting all letters to lowercase. NoOperation: indicates that no conversion is performed. |
Tag | Optional. You can add additional custom tags to the metrics collected by the integration module. |
Cross-Account Collection | Current account role: custom role, used to obtain the temporary key for the current account. Target account role: custom role, used to obtain the temporary key for the target account. Target account UIN: root account ID of the target account. |
Metric Relabel Configuration | Optional. Native metricRelabelings configuration for Prometheus Operator. The configuration method is the same as metric_relabel_configs in Prometheus scraping configuration, with only different naming conventions for certain fields. |
4. In the scraping task, click the Integrated tab and wait for 2 to 3 minutes. You can see that Operation Status is changed to Deployed. In Targets, you can view specific data scraping targets. Click Metric Details, and you can see the scraped monitoring metrics.
Step 3: Viewing Monitoring Data
1. Return to the TMP instance details page, click the Basic Information tab, and bind a TencentCloud Managed Service for Grafana (TCMG) instance in the Grafana card. If no TCMG instance exists, create one first. For detailed creation instructions, see TencentCloud Managed Service for Grafana.
Note:
The VPC network and subnet of the bound or newly created TCMG instance must match the vpcId and subnetId specified in item 4 of Step 1. Otherwise, network connectivity issues occur.
2. After a TCMG instance is bound, choose Data Collection > Integration Center. On the Integration Center page, locate and click Cloud Monitor, and then choose Dashboard > Dashboard Operation > Install/Upgrade Dashboard, and click Install/Upgrade to install the Grafana dashboard.
3. Select Integrated, and click the Grafana icon in the integrated list to automatically open the Cloud Monitor integration dashboard list. Select TDMQ for MQTT to view instance-related monitoring data.
Help and Support
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback