tccli-intl-en 3.0.1237.1__py2.py3-none-any.whl → 3.0.1282.1__py2.py3-none-any.whl

tccli/services/monitor/v20180724/examples.json

@@ -58,10 +58,118 @@
     ],
     "CreateExporterIntegration": [
       {
-        "document": " ",
-        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"KubeType\": 3,\n    \"ClusterId\": \"cls-xx\",\n    \"Kind\": \"blackbox-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"test\\\",\\\"kind\\\":\\\"blackbox-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"module\\\":\\\"http_get\\\",\\\"urls\\\":[\\\"xx\\\"]}}}\"\n}",
-        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"redis-exporter\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
-        "title": "Creating an exporter integration"
+        "document": "The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `emr-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. kind is the integration type, required and fixed as `emr-exporter` here<br> 3.2. spec.job is the scrape configuration, required in yaml format. For details, see the EMR integration documentation (https://www.tencentcloud.com/document/product/248/65343)",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"emr-exporter\",\n    \"Content\": \"{\\\"kind\\\":\\\"emr-exporter\\\",\\\"spec\\\":{\\\"job\\\":\\\"job_name: emr-example-job\\\\nmetrics_path: /metrics\\\\nemr_sd_configs:\\\\n- region: ap-guangzhou\\\\n  instance_ids: \\\\n    - emr-test\\\\nrelabel_configs:\\\\n- regex: __meta_emr_(.*)\\\\n  replacement: $1\\\\n  action: labelmap\\\"}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"emr-example-job\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating an EMR Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `cdwch-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. kind is the integration type, required and fixed as `cdwch-exporter` here<br> 3.2. spec.job is the scrape configuration, required in yaml format. It is recommended to refer to the reference input example and only modify the job_name and instance_ids.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"cdwch-exporter\",\n    \"Content\": \"{\\\"kind\\\":\\\"cdwch-exporter\\\",\\\"spec\\\":{\\\"job\\\":\\\"job_name: cdwch-example-job\\\\nmetrics_path: /metrics\\\\ncdwch_sd_configs:\\\\n- region: ap-guangzhou\\\\n  instance_ids: \\\\n    - cdwch-test\\\\nrelabel_configs:\\\\n- regex: __meta_cdwch_(.*)\\\\n  replacement: $1\\\\n  action: labelmap\\\"}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"cdwch-example-job\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Cdwch Integration"
+      },
+      {
+        "document": " Install a no-auth agent to access the Prometheus native API over the private network without authentication.<br> Once created, you can call the DescribeExporterIntegrations API to obtain the integrated private IP:Port address through the InstanceDesc parameter. This address can replace the Prometheus instance address to achieve authentication-free access.<br>  The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `raw-job` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. kind is the integration type, required and fixed as `raw-job` here<br> 3.2. spec.job is the scrape configuration, required in yaml format. For details, see the documentation (https://www.tencentcloud.com/document/product/248/62393#native-job-configuration)",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"raw-job\",\n    \"Content\": \"{\\\"kind\\\":\\\"raw-job\\\",\\\"spec\\\":{\\\"job\\\":\\\"job_name: test-job\\\\nscrape_interval: 30s\\\\nstatic_configs:\\\\n- targets:\\\\n  - 127.0.0.1:9090\\\"}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"test-job\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Scrape Job"
+      },
+      {
+        "document": "The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `kafka-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `kafka-exporter`<br> 3.3. spec.instanceSpec.servers is the address of the Kafka instance, required. You can fill in more than one. We recommend one instance per integration.<br> 3.4. spec.instanceSpec.version is the Kafka instance version, which is optional. An error will be reported if not filled in for some versions, such as 0.10.2.0.<br> 3.5. spec.instanceSpec.labels is used to add custom tags to metrics, in key-value pair format, optional<br> 3.6. spec.exporterSpec.topicFilter is used for filtering topics. It is optional and collects all by default. After filling in a regular expression, only eligible topics are collected.<br> 3.7. spec.exporterSpec.groupFilter is used for filtering groups. It is optional and defaults to collecting all. After filling in regular expression, only eligible groups will be collected.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"kafka-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"kafka-test\\\",\\\"kind\\\":\\\"kafka-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"servers\\\":[\\\"127.0.0.1:8080\\\"],\\\"version\\\":\\\"0.10.2.0\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}},\\\"exporterSpec\\\":{\\\"topicFilter\\\":\\\"topic.*\\\",\\\"groupFilter\\\":\\\"group.*\\\"}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"kafka-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Kafka Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `mysql-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `mysql-exporter`<br> 3.3. spec.instanceSpec.user is the username of the MySQL instance, required.<br> 3.4. spec.instanceSpec.password is the password for the MySQL instance, required<br> 3.5. spec.instanceSpec.address is the connection address of the MySQL instance, required<br> 3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"mysql-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"mysql-test\\\",\\\"kind\\\":\\\"mysql-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"user\\\":\\\"root\\\",\\\"password\\\":\\\"password\\\",\\\"address\\\":\\\"127.0.0.1:8080\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"mysql-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a MySQL Integration"
+      },
+      {
+        "document": " The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `redis-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `redis-exporter`<br> 3.3. spec.instanceSpec.address is the connection address of the Redis instance, required.<br> 3.4. spec.instanceSpec.password is the password for the Redis instance, required<br> 3.5. spec.instanceSpec.labels Used to add custom tags to metrics, key-value pair type, optional",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"redis-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"redis-test\\\",\\\"kind\\\":\\\"redis-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"address\\\":\\\"127.0.0.1:8080\\\",\\\"password\\\":\\\"password\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"redis-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Redis Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `consul-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `consul-exporter`<br> 3.3. spec.instanceSpec.server is the address of the Consul instance, required.<br> 3.4. spec.instanceSpec.labels Use custom tags for metrics, key-value pair type, optional",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"consul-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"consul-test\\\",\\\"kind\\\":\\\"consul-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"server\\\":\\\"1.1.1.1:8080\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"consul-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Consul Integration"
+      },
+      {
+        "document": "  The parameter descriptions are as follows:<br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.<br> 2. The Kind parameter is fixed as `mongodb-exporter` and is required.<br> 3. The parameter format of Content is as shown in the example. The details are as follows:<br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `mongodb-exporter`<br> 3.3. spec.instanceSpec.user is the username of the MongoDB instance, required<br> 3.4. spec.instanceSpec.password is the password of the MongoDB instance, required<br> 3.5. spec.instanceSpec.servers is the connection address of the MongoDB instance, required, you can fill in more than one, separate with commas<br> 3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional<br> 3.7. spec.exporterSpec.collectors is the collection configuration of the exporter, fillable, an array of strings. This example shows you how to fill in all values. Among them, `database` means enabling the collection of database metrics, `collection` means enabling the collection of collection metrics, `topmetrics` means enabling the collection of header metric information, `indexusage` means enabling the collection of index usage statistics, `connpoolstats` means enabling the collection of connection pool statistics.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"mongodb-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"mongodb-test\\\",\\\"kind\\\":\\\"mongodb-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"user\\\":\\\"root\\\",\\\"password\\\":\\\"password\\\",\\\"servers\\\":[\\\"127.0.0.1:8080\\\",\\\"127.0.0.2:8080\\\"],\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}},\\\"exporterSpec\\\":{\\\"collectors\\\":[\\\"database\\\",\\\"collection\\\",\\\"topmetrics\\\",\\\"indexusage\\\",\\\"connpoolstats\\\"]}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"mongodb-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating MongoDB Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `rocketmq-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`  <br> 3.2. kind is the integration type, required and fixed as `rocketmq-exporter` here  <br> 3.3. spec.instanceSpec.address is the address of the RocketMQ instance, required. You can fill in more than one, separate them with a semicolon.  <br> 3.4. spec.instanceSpec.version is the version of the RocketMQ instance, required, such as V4_9_4  <br> 3.5. spec.instanceSpec.labels Used to add custom tags to metrics, key-value pair type, optional<br>",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"rocketmq-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"rocketmq-test\\\",\\\"kind\\\":\\\"rocketmq-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"address\\\":\\\"127.0.0.1:8080;127.0.0.2:8080\\\",\\\"version\\\":\\\"V4_9_4\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"rocketmq-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a RocketMQ Integration"
+      },
+      {
+        "document": "Installing the Graphite Exporter enables the conversion of Graphite metrics into Prometheus metrics.<br> After creation, you can call the DescribeExporterIntegrations API to get the private IP address:Port of the integration through the InstanceDesc parameter.<br> The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `graphite-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `graphite-exporter`<br> 3.3. spec.instanceSpec.isStrictMatch indicates whether to perform strict matching with mappingConfig. This field is optional and defaults to false.<br> 3.4. spec.instanceSpec.mappingConfig is the mapping configuration, which can define the name and label of Prometheus metrics. For details, see the official documentation (https://github.com/prometheus/graphite_exporter#yaml-config)",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"graphite-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"graphite-test\\\",\\\"kind\\\":\\\"graphite-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"isStrictMatch\\\":true,\\\"mappingConfig\\\":\\\"mappings:\\\\n- match: test.dispatcher.*.*.*\\\\n  name: dispatcher_events_total\\\\n  labels:\\\\n    action: $2\\\\n    job: test_dispatcher\\\\n    outcome: $3\\\\n    processor: $1\\\\n- match: \\\\\\\"*.signup.*.*\\\\\\\"\\\\n  name: signup_events_total\\\\n  labels:\\\\n    job: ${1}_server\\\\n    outcome: $3\\\\n    provider: $2\\\\n- match: \\\\\\\"servers.(.*).networking.subnetworks.transmissions.([a-z0-9-]+).(.*)\\\\\\\"\\\\n  match_type: regex\\\\n  name: \\\\\\\"servers_networking_transmissions_${3}\\\\\\\"\\\\n  labels: \\\\n    hostname: ${1}\\\\n    device: ${2}\\\"}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"graphite-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Graphite Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `qcloud-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `qcloud-exporter`<br> 3.3. spec.instanceSpec.region indicates the region where the cloud product is located. This parameter is required. For example, to collect Cloud products in the Guangzhou region, you can set to `Guangzhou` or `ap-guangzhou`. The parameter will be converted to the label of the object, named `instance-region`.<br> 3.4. spec.instanceSpec.delaySeconds indicates data collection delay, an integer in seconds (optional, default is 0). When the value is 0, the timestamp of the original data point will be ignored and replaced with the time when the data point is pulled during integration. When the value is greater than 0, the data point will retain its original timestamp, and the data will inevitably be delayed by the set time.<br> 3.5. spec.instanceSpec.reload_interval_minutes indicates the instance refresh interval, an integer in minutes, required and must be greater than or equal to 10. New additions of cloud product instances or modifications to cloud tags will be reflected in metrics after instance refresh, with up to one instance refresh interval to wait.<br> 3.6. spec.instanceSpec.useRole indicates whether to use a service role. It is a boolean type and required. The current logic always uses a service role, so it must be set to `true`.<br> 3.7. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional<br> 3.8. spec.exporterSpec.[Cloud Product] indicates whether to collect the corresponding cloud service. Boolean type, `true` means collecting this cloud service. Cloud service codes and their meanings: `cvm`: Cloud Virtual Machine, `cbs`: Cloud Block Storage, `lb_public`: Cloud Load Balancer (public network), `lb_private`: Cloud Load Balancer (private network), `tgw_set`: Cloud Load Balancer (exclusive cluster), `cmongo`: MongoDB Database, `cdb`: MySQL Database (CDB), `redis`: Redis Database (CKV edition), `redis_mem`: Redis Database (in-memory edition), `tendis`: Tendis, `xstor`: CTSDB (InfluxDB edition), `mariadb`: MariaDB Database, `postgres`: PostgreSQL Database, `tdmysql`: TDSQL MySQL edition, `cynosdb_mysql`: TDSQL-C MySQL, `sqlserver`: SQL Server Database, `nat_gateway`: NAT Gateway, `ckafka`: CKafka, `rocketmq`: RocketMQ (new metric), `lb`: Elastic IP, `vpngw`: VPN Gateway, `vpnx`: VPN Tunnel, `vpc_net_detect`: Network Probe, `cdn`: CDN, `ov_cdn`: CDN (overseas), `cos`: COS, `dc`: Direct Connect - Physical Connection, `dcx`: Direct Connect - Dedicated Tunnel, `dcg`: Direct Connect - Direct Connect Gateway, `lighthouse`: Tencent Cloud Lighthouse, `nacos`: Nacos, `zookeeper`: Zookeeper, `ces`: Elasticsearch, `dts`: Data Transfer Service, `vbc`: Cloud Connect Network, `gaap`: Global Application Acceleration Platform, `waf`: Web Application Firewall, `cfs`: Cloud File Storage, `bwp`: Bandwidth Package, `scf_v2`: Serverless Cloud Function (alias), `vod`: Video on Demand (VOD), `cls`: Cloud Log Service (CLS) - Log Topic, `apigateway`: API Gateway, `ti_traintask`: TI-ONE (task-based modeling), `ti_notebook`: TI-ONE (Notebook), `ti_model`: TI-ONE (online service), `self`: Collector self-monitoring.<br> 3.9. spec.scrapeSpec.relabelConfigs is used to add the `metric_relabel_configs` configuration, which is optional. See the configuration example (https://www.tencentcloud.com/document/product/248/63002#29fe272b-ac9e-4932-b6dc-972c2b1ef9dc).",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"qcloud-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"test-qcloud\\\",\\\"kind\\\":\\\"qcloud-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"region\\\":\\\"Guangzhou\\\",\\\"delaySeconds\\\":0,\\\"reload_interval_minutes\\\":10,\\\"useRole\\\":true,\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}},\\\"exporterSpec\\\":{\\\"cvm\\\":true,\\\"cbs\\\":true},\\\"scrapeSpec\\\":{\\\"relabelConfigs\\\":\\\"metric_relabel_configs:\\\\n- action: labeldrop\\\\n  regex: tmp_test_label\\\\n\\\"}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"test-qcloud\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating Cloud Monitoring Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `memcached-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `memcached-exporter`<br> 3.3. spec.instanceSpec.address is the domain name or IP address of the Memcached instance, required.<br> 3.4. spec.instanceSpec.labels Use custom tags for metrics, key-value pair type, optional<br>",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"memcached-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"memcached-test\\\",\\\"kind\\\":\\\"memcached-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"address\\\":\\\"127.0.0.1:8080\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"memcached-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Memcached Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `postgres-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `postgres-exporter`<br> 3.3. spec.instanceSpec.user is the username of the PostgreSQL instance, required<br> 3.4. spec.instanceSpec.password is the password of the PostgreSQL instance, required<br> 3.5. spec.instanceSpec.address is the connection address of the PostgreSQL instance, required<br> 3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional<br>",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"postgres-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"postgresql-test\\\",\\\"kind\\\":\\\"postgres-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"user\\\":\\\"user\\\",\\\"password\\\":\\\"password\\\",\\\"address\\\":\\\"127.0.0.1:8080\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"postgresql-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating PostgreSQL Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `blackbox-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `blackbox-exporter`<br> 3.3. spec.instanceSpec.module is the detection method, required. Optional values: `http_get`, `http_post`, `tcp`, `ssh`, `ping`.<br> 3.4. spec.instanceSpec.urls is the detection target, a string array, required. The target format can be host:port, http://abc, or https://abc.<br> 3.5. spec.instanceSpec.noAllowRedirect controls whether to forbid redirection. It is a boolean type, optional, and only applicable to the detection methods `http_get` and `http_post`. If true, it means redirection is forbidden. You can leave it blank, and it defaults to false.<br> 3.6. spec.instanceSpec.insecureSkipVerify controls whether to disable target certificate authentication. It is a boolean type and optional, only applicable to the detection methods `http_get` and `http_post`. true indicates that it is disabled. You can leave it blank, and it defaults to false.<br> 3.7. spec.instanceSpec.headers adds headers when probing the target. It uses key-value pairs, is optional, and only applicable to the `http_get` and `http_post` detection methods.<br> 3.8. spec.instanceSpec.labels is used to add custom tags to metrics, key-value pair type, optional<br> 3.9. spec.scrapeSpec.interval is used for custom check interval, optional, 15s is selected by default<br>",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"blackbox-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"test-blackbox\\\",\\\"kind\\\":\\\"blackbox-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"module\\\":\\\"http_get\\\",\\\"urls\\\":[\\\"host:port\\\",\\\"http://abc\\\",\\\"https://abc\\\"],\\\"noAllowRedirect\\\":false,\\\"insecureSkipVerify\\\":true,\\\"headers\\\":{\\\"Authorization\\\":\\\"Basic <Credentials>\\\",\\\"test\\\":\\\"test\\\"},\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}},\\\"scrapeSpec\\\":{\\\"interval\\\":\\\"15s\\\"}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"test-blackbox\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a Health Check Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `es-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `es-exporter` here<br> 3.3. spec.instanceSpec.user is the username of ElasticSearch, required<br> 3.4. spec.instanceSpec.password is the ElasticSearch password, required<br> 3.5. spec.instanceSpec.url is the ElasticSearch connection address, required<br> 3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional<br> 3.7. spec.exporterSpec.all indicates whether to query statistical information of all nodes in a cluster. It is a boolean type, optional, and the default value is false. If false, it only queries statistical information of connected nodes.<br> 3.8. spec.exporterSpec.indices indicates whether to query index statistics for all in a cluster, boolean type, optional, default value is false<br> 3.9. spec.exporterSpec.indicesSettings indicates whether to query statistical information of all index configurations in a cluster, boolean type, optional, default value is false<br> 3.10. spec.exporterSpec.shards indicates whether to query index statistics of all in a cluster, including shard level statistical information. Boolean type, optional, default value is false.<br> 3.11. spec.exporterSpec.snapshots indicates whether to query cluster snapshot statistical information. It is a boolean type, optional, and the default value is false.<br> 3.12. spec.exporterSpec.clusterSettings indicates whether to query cluster configuration statistical information, boolean type, optional, default value is false",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"es-exporter\",\n    \"Content\": \"{\\\"name\\\":\\\"es-test\\\",\\\"kind\\\":\\\"es-exporter\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"user\\\":\\\"root\\\",\\\"password\\\":\\\"password\\\",\\\"url\\\":\\\"http://127.0.0.1:8080\\\",\\\"labels\\\":{\\\"labelKey\\\":\\\"labelValue\\\",\\\"test\\\":\\\"test\\\"}},\\\"exporterSpec\\\":{\\\"all\\\":true,\\\"indices\\\":true,\\\"indicesSettings\\\":true,\\\"shards\\\":true,\\\"snapshots\\\":true,\\\"clusterSettings\\\":true}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"es-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating an ElasticSearch Integration"
+      },
+      {
+        "document": "Install a no-auth agent to access the Prometheus native API over the private network without authentication.<br> Once created, you can call the DescribeExporterIntegrations API to obtain the integrated private IP:Port address through the InstanceDesc parameter. This address can replace the Prometheus instance address to achieve authentication-free access.<br> The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `auth-proxy` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. name is the integration name, required and globally unique, and must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 3.2. kind is the integration type, required and fixed as `auth-proxy`<br> 3.3. spec.instanceSpec.enableSelfMonitor indicates whether to collect self-monitoring metrics. This field is optional and the default is false. The self-monitoring metric is auth_proxy_http_requests_total{result=~\"success|error\"}, which counts request quantity for success or failure.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"auth-proxy\",\n    \"Content\": \"{\\\"name\\\":\\\"auth-test\\\",\\\"kind\\\":\\\"auth-proxy\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"enableSelfMonitor\\\":true}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"auth-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a No-Auth Proxy Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `cvm-http-sd-exporter` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. kind is the integration type, required and fixed as `cvm-http-sd-exporter`<br> 3.2. spec.job is the scrape configuration, required in yaml format. For specific configuration, see the scraping configuration instructions (https://www.tencentcloud.com/document/product/248/62393#.60cvm_sd_config.60-configuration)",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"cvm-http-sd-exporter\",\n    \"Content\": \"{\\\"kind\\\":\\\"cvm-http-sd-exporter\\\",\\\"spec\\\":{\\\"job\\\":\\\"job_name: example-job-name\\\\nmetrics_path: /metrics\\\\ncvm_sd_configs:\\\\n- region: ap-singapore\\\\n  ports:\\\\n  - 9100\\\\n  filters:         \\\\n  - name: tag:example_tag_key\\\\n    values: \\\\n    - example_tag_value\\\\nrelabel_configs: \\\\n- source_labels: [__meta_cvm_instance_state]\\\\n  regex: RUNNING\\\\n  action: keep\\\\n- regex: __meta_cvm_tag_(.*)\\\\n  replacement: $1\\\\n  action: labelmap\\\\n- source_labels: [__meta_cvm_region]\\\\n  target_label: region\\\\n  action: replace\\\"}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"example-job-name\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating a CVM Scrape Job Integration"
+      },
+      {
+        "document": "To ensure the CVM instance and Prometheus instance are connected via private network (for example, under the same VPC) and the CVM instance has Tencent Cloud Automation Tools (TAT) installed (https://www.tencentcloud.com/document/product/1147/46042).<br> The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `cvm-node-exporter-sd` and is required.  <br> 3. The parameter format of Content is as shown in the example. The details are as follows:  <br> 3.1. kind is the integration type, required and fixed as `cvm-node-exporter-sd` here<br> 3.2. spec.job is the scrape configuration, required in yaml format. You can refer to the input example, where instance_ids can contain multiple CVM instance ids.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"Kind\": \"cvm-node-exporter-sd\",\n    \"Content\": \"{\\\"kind\\\":\\\"cvm-node-exporter-sd\\\",\\\"spec\\\":{\\\"job\\\":\\\"job_name: node-test\\\\ninstance:\\\\n  - region: ap-chengdu\\\\n    instance_ids:\\\\n      - ins-a\\\\n      - ins-b\\\\n\\\"}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"node-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating CVM Node Exporter Integration"
+      },
+      {
+        "document": "The parameter descriptions are as follows:  <br> 1. The InstanceId parameter is the Prometheus Instance ID and is required.  <br> 2. The Kind parameter is fixed as `nginx-ingress` and is required.  <br> 3. ClusterId is the cluster ID associated with the Prometheus instance where Ingress NGINX Controller is deployed, required<br> 4. KubeType is the cluster type corresponding to ClusterId, required. 1 means tke cluster, 2 or 3 means eks cluster.<br> 5. The parameter format of Content is as shown in the example. The details are as follows:  <br> 5.1. kind is the integration type, required and fixed as `nginx-ingress`<br> 5.2. name is the integration name, required and globally unique, must match the regex `^[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*$`<br> 5.3. spec.instanceSpec.namespace is the namespace where Ingress NGINX Controller resides, required<br> 5.4. spec.instanceSpec.name is the name of the Ingress NGINX Controller, required. Use the name of the Deployment or DaemonSet.<br> 5.5. spec.instanceSpec.workload is the cluster object type for Ingress NGINX Controller, required, such as deployment or daemonset.<br>",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreateExporterIntegration\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-1\",\n    \"ClusterId\": \"cls-test\",\n    \"KubeType\": 1,\n    \"Kind\": \"nginx-ingress\",\n    \"Content\": \"{\\\"kind\\\":\\\"nginx-ingress\\\",\\\"name\\\":\\\"ingress-test\\\",\\\"spec\\\":{\\\"instanceSpec\\\":{\\\"namespace\\\":\\\"namespace\\\",\\\"name\\\":\\\"controller-name\\\",\\\"workLoad\\\":\\\"deployment\\\"}}}\"\n}",
+        "output": "{\n    \"Response\": {\n        \"Names\": [\n            \"ingress-test\"\n        ],\n        \"RequestId\": \"xyz\"\n    }\n}",
+        "title": "Creating Ingress NGINX Controller Integration"
       }
     ],
     "CreateGrafanaInstance": [
@@ -104,6 +212,14 @@
         "title": "Creating a Prometheus agent"
       }
     ],
+    "CreatePrometheusAlertGroup": [
+      {
+        "document": "This example shows you how to create an alert rule using a notification template.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: CreatePrometheusAlertGroup\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-7vp71mk0\",\n\"GroupName\": \"Alarm Grouping Test\"\n    \"AMPReceivers\": [\n        \"notice-xxxxxx\"\n    ],\n    \"Rules\": [\n        {\n\"RuleName\": \"Rule-1\",\n            \"Labels\": [\n                {\n                    \"Key\": \"k1\",\n                    \"Value\": \"v1\"\n                }\n            ],\n            \"Annotations\": [\n                {\n                    \"Key\": \"summary\",\n                    \"Value\": \"{{$value}}\"\n                },\n                {\n                    \"Key\": \"describe\",\n\"Value\": \"Rule 1 Alarm\"\n                }\n            ],\n            \"Expr\": \"expr1\"\n        }\n    ]\n}",
+        "output": "{\n    \"Response\": {\n        \"GroupId\": \"alert-2zvqof1a\",\n        \"RequestId\": \"02c92b99-abc9-431b-8b08-42b9977d51cf\"\n    }\n}",
+        "title": "Creating an Alert Rule Using a Notification Template"
+      }
+    ],
     "CreatePrometheusAlertPolicy": [
       {
         "document": "This example shows you how to create an alerting rule.",
@@ -268,6 +384,14 @@
         "title": "Deleting alarm policy group"
       }
     ],
+    "DeletePrometheusAlertGroups": [
+      {
+        "document": "This example shows you how to delete an Alert group",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: DeletePrometheusAlertGroups\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-7vp71mk0\",\n    \"GroupIds\": [\n        \"alert-ol72w8vy\"\n    ]\n}",
+        "output": "{\n    \"Response\": {\n        \"RequestId\": \"09cffdc9-047e-45c5-b0eb-6d7cbfee5048\"\n    }\n}",
+        "title": "Deleting an Alert Group"
+      }
+    ],
     "DeletePrometheusAlertPolicy": [
       {
         "document": "This example shows you how to delete a Prometheus alerting rule.",
@@ -622,6 +746,14 @@
         "title": "Listing Prometheus agents"
       }
     ],
+    "DescribePrometheusAlertGroups": [
+      {
+        "document": "This example shows you how to list ALL alert groups under an instance, including enabled and disabled ones.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: DescribePrometheusAlertGroups\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-xxxxxxxx\"\n}",
+        "output": "{\n    \"Response\": {\n        \"AlertGroupSet\": [\n            {\n                \"AMPReceivers\": [],\n                \"CreatedAt\": \"2023-08-01T20:29:56+08:00\",\n                \"CustomReceiver\": {\n                    \"Type\": \"\",\n                    \"Url\": \"\"\n                },\n                \"GroupId\": \"alert-xxxxxxxx\",\n\"GroupName\": \"Query Alerts Group Trial-1\"\n                \"Rules\": [\n                    {\n                        \"Annotations\": [\n                            {\n                                \"Key\": \"summary\",\n                                \"Value\": \"{{$value}}\"\n                            }\n                        ],\n                        \"Duration\": \"\",\n                        \"Expr\": \"expr1\",\n                        \"Labels\": [\n                            {\n                                \"Key\": \"_interval_\",\n                                \"Value\": \"10m\"\n                            }\n                        ],\n\"RuleName\": \"Rule -1\",\n                        \"State\": 2\n                    }\n                ],\n                \"TemplateId\": \"\",\n                \"UpdatedAt\": \"2023-08-01T20:29:56+08:00\"\n            }\n        ],\n        \"RequestId\": \"bc70036f-db50-4b46-abbc-bd41eeb06f7a\",\n        \"TotalCount\": 1\n    }\n}",
+        "title": "List All Alert Groups under an Instance"
+      }
+    ],
     "DescribePrometheusAlertPolicy": [
       {
         "document": "describe prometheus instance alert policy list",
@@ -1160,6 +1292,22 @@
         "title": "Updating the status of a Prometheus agent"
       }
     ],
+    "UpdatePrometheusAlertGroup": [
+      {
+        "document": "",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: UpdatePrometheusAlertGroup\n<Common request parameters>\n\n{\n    \"GroupId\": \"alert-34xae12s\",\n    \"InstanceId\": \"prom-7vp71mk0\",\n\"GroupName\": \"Update alarm group test\"\n    \"AMPReceivers\": [\n        \"notice-xxxxxx\"\n    ],\n    \"Rules\": [\n        {\n\"RuleName\": \"Rule-1\",\n            \"Labels\": [\n                {\n                    \"Key\": \"k1\",\n                    \"Value\": \"v1\"\n                }\n            ],\n            \"Annotations\": [\n                {\n                    \"Key\": \"summary\",\n                    \"Value\": \"{{$value}}\"\n                },\n                {\n                    \"Key\": \"describe\",\n\"Value\": \"Rule 1 Alarm\"\n                }\n            ],\n            \"Expr\": \"expr1\"\n        }\n    ]\n}",
+        "output": "{\n    \"Response\": {\n        \"GroupId\": \"alert-34xae12s\",\n        \"RequestId\": \"02c92b99-abc9-431b-8b08-42b9977d51cf\"\n    }\n}",
+        "title": "Updating Alert Group"
+      }
+    ],
+    "UpdatePrometheusAlertGroupState": [
+      {
+        "document": "This example shows you how to disable alarm grouping in settings.",
+        "input": "POST / HTTP/1.1\nHost: monitor.tencentcloudapi.com\nContent-Type: application/json\nX-TC-Action: UpdatePrometheusAlertGroupState\n<Common request parameters>\n\n{\n    \"InstanceId\": \"prom-7vp71mk0\",\n    \"GroupIds\": [\n        \"alert-ol72w8vy\"\n    ],\n    \"GroupState\": 3\n}",
+        "output": "{\n    \"Response\": {\n        \"RequestId\": \"a4797141-a4f9-43d4-b4ca-09d72bb48f8d\"\n    }\n}",
+        "title": "Setting Alarm Group Disabling"
+      }
+    ],
     "UpdatePrometheusScrapeJob": [
       {
         "document": " ",