tencent cloud

APIs

Cloud Virtual Machine
History
Introduction
API Category
Making API Requests
Region APIs
Instance APIs
Cloud Hosting Cluster APIs
Image APIs
Instance Launch Template APIs
Placement Group APIs
Key APIs
Security Group APIs
Network APIs
Data Types
Error Codes
Tencent Cloud Lighthouse
History
Introduction
API Category
Making API Requests
Image APIs
Firewall APIs
Key APIs
Instance APIs
CCN APIs
Snapshot APIs
Other APIs
Cloud Disk APIs
Scene APIs
Package APIs
Quota APIs
Region APIs
Data Types
Error Codes
Auto Scaling
History
Introduction
API Category
Making API Requests
Scaling Group APIs
Scaling Group Instances APIs
Launch Configuration APIs
Scheduled Action APIs
Alarm Trigger Policy APIs
Notification APIs
Lifecycle Hook APIs
Instance Refresh APIs
Other APIs
Data Types
Error Codes
Batch Compute
History
Introduction
API Category
Making API Requests
Compute Environment APIs
Configuration Viewing-related APIs
Task Template-related APIs
Job-related APIs
Data Types
Error Codes
Tencent Cloud Automation Tools
History
Introduction
API Category
Making API Requests
Remote Command APIs
Scheduled Execution APIs
Managed Instance APIs
Scenario APIs
Statistics APIs
Data Types
Error Codes
Edge Computing Machine
History
API Category
Making API Requests
Region APIs
Module APIs
Instance APIs
Image APIs
VPC APIs
Subnet APIs
Route Table APIs
CLB APIs
ENI APIs
EIP APIs
HAVIP APIs
Other API
Key APIs
Security Group APIs
Data Types
Error Codes
Tencent Kubernetes Engine
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
Tencent Container Registry
History
Introduction
API Category
Making API Requests
Instance Management APIs
Namespace APIs
Access Control APIs
Instance Synchronization APIs
Tag Retention APIs
Trigger APIs
Helm Chart APIs
Image Repository APIs
Custom Account APIs
Data Types
Error Codes
Tencent Cloud Elastic Microservice
History
Introduction
API Category
Making API Requests
Environment APIs
ModifyIngress
Resource APIs
Application APIs
Service APIs
Application Deployment APIs
Access Policy APIs
Configuration file APIs
Log collecting APIs
Scaling Rule APIs
Application Version APIs
Other APIs
Workload APIs
Data Types
Error Codes
Serverless Cloud Function
History
Introduction
API Category
Making API Requests
Other APIs
Namespace APIs
Layer Management APIs
Async Event Management APIs
Trigger APIs
Function APIs
Function and Layer Status Description
Data Types
Error Codes
Event Bridge
History
Introduction
API Category
Making API Requests
Delivery Target APIs
Event Bus APIs
Event Rule APIs
Event Connector APIs
Data Transformer APIs
Event Storage APIs
Data Types
Error Codes
Cloud Object Storage
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
Cloud File Storage
History
Introduction
API Category
Snapshot APIs
File system APIs
Lifecycle APIs
Other APIs
Data Flow APIs
Making API Requests
Permission Group APIs
Service APIs
Scaling APIs
Data Migration APIs
Data Types
Error Codes
Cloud Block Storage
History
Introduction
API Category
Making API Requests
Snapshot APIs
Cloud Disk APIs
Data Types
Error Codes
Cloud HDFS
History
Introduction
API Category
Making API Requests
Other APIs
Permission group APIs
Permission rule APIs
Mount point APIs
Lifecycle rule APIs
File system APIs
Restoration task APIs
Data Types
Error Codes
Cloud Log Service
History
Introduction
API Category
Making API Requests
Topic Management APIs
Log Set Management APIs
Index APIs
Topic Partition APIs
Machine Group APIs
Collection Configuration APIs
Log APIs
Metric APIs
Alarm Policy APIs
Data Processing APIs
Kafka Protocol Consumption APIs
Kafka Task APIs
Kafka Data Subscription APIs
COS Task APIs
SCF Delivery Task APIs
Scheduled SQL Analysis APIs
COS Data Import Task APIs
Data Types
Error Codes
TDSQL-C for MySQL
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
TencentDB for MySQL
History
Introduction
API Category
Instance APIs
Making API Requests
Data Import APIs
Database Proxy APIs
Database Audit APIs
Security APIs
Task APIs
Backup APIs
Account APIs
Rollback APIs
Parameter APIs
Database APIs
Monitoring APIs
Log-related API
Data Types
Error Codes
TencentDB for MariaDB
History
Introduction
API Category
Making API Requests
Security Group APIs
Other APIs
Account APIs
Parameter Management APIs
Monitoring Management APIs
Instance Management APIs
Backup and Restoration APIs
Data Types
Error Codes
TencentDB for PostgreSQL
History
Introduction
API Category
Making API Requests
Instance APIs
Read-only Replica APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
TencentDB for SQL Server
History
Introduction
API Category
Making API Requests
Sales and fee related APIs
Instance Management related APIs
Operation and maintenance management related APIs
Network management related APIs
Account management related APIs
Database management related APIs
Security group management related APIs
Data security encryption related APIs
Parameter configuration related APIs
Extended Event related APIs
Log management related APIs
Read only instance management related APIs
Publish and subscribe related APIs
Backup related APIs
Data migration (cold standby migration) related APIs
Rollback related APIs
Data migration (DTS old version) related APIs
SQL Server Integration Services (SSIS) related APIs
Data Types
Error Codes
TDSQL for MySQL
History
Introduction
API Category
Security Group APIs
Other APIs
Making API Requests
TDSQL APIs
Data Types
Error Codes
Tencent Cloud Distributed Cache (Redis OSS-Compatible)
History
Introduction
API Category
Making API Requests
Instance APIs
Parameter Management APIs
Other APIs
Backup and Restoration APIs
Region APIs
Monitoring and Management APIs
Log APIs
Data Types
Error Codes
TencentDB for MongoDB
History
Introduction
API Category
Making API Requests
Instance APIs
Backup APIs
Account APIs
Other APIs
Task APIs
Introduction
Data Types
Error Codes
TencentDB for TcaplusDB
History
Introduction
API Category
Making API Requests
Table Group APIs
Other APIs
Table APIs
Cluster APIs
Data Types
Error Codes
Data Transfer Service
History
Introduction
API Category
Making API Requests
(NewDTS) Data Migration APIs
Data Sync APIs
Data Consistency Check APIs
(NewDTS) Data Subscription APIs
Data Types
Error Codes
DTS API 2018-03-30
TencentDB for DBbrain
History
Introduction
Introduction
API Category
Making API Requests
Session Killing APIs
Exception Detection APIs
Other APIs
Redis related APIs
Health Report Email Sending APIs
Space Analysis APIs
Security Audit APIs
Slow Log Analysis APIs
Database Audit APIs
Data Types
Error Codes
DBbrain APIs 2019-10-16
Virtual Private Cloud
History
Introduction
API Category
Making API Requests
VPC APIs
Route Table APIs
Elastic Public IP APIs
Elastic IPv6 APIs
Highly Available Virtual IP APIs
ENI APIs
Bandwidth Package APIs
NAT Gateway APIs
Direct Connect Gateway APIs
Cloud Connect Network APIs
Network ACL APIs
Network Parameter Template APIs
Network Detection-Related APIs
Flow Log APIs
Gateway Traffic Monitor APIs
Private Link APIs
Traffic Mirroring APIs
Other APIs
Subnet APIs
VPN Gateway APIs
Security Group APIs
Snapshot Policy APIs
Error Codes
Data Types
Cloud Load Balancer
History
Introduction
API Category
Instance APIs
Listener APIs
Backend Service APIs
Target Group APIs
Redirection APIs
Other APIs
Classic CLB APIs
Load Balancing APIs
Making API Requests
Data Types
Error Codes
CLB API 2017
Direct Connect
History
Introduction
API Category
Making API Requests
Direct Connect APIs
Data Types
Error Codes
Content Delivery Network
History
Introduction
API Category
Content Management APIs
Real-time Log APIs
Service Query APIs
Data Query APIs
Making API Requests
Log Query APIs
Domain Name Management APIs
Configuration Management APIs
Obsoleted APIs
Other APIs
Data Types
Error Codes
Global Application Acceleration Platform
History
Introduction
API Category
Rule APIs
Connection Group APIs
Making API Requests
Origin Server APIs
Listener APIs
Connection APIs
Certificate APIs
Other APIs
Data Types
Error Codes
Tencent Cloud Firewall
History
Introduction
API Category
Making API Requests
Intrusion Defense APIs
Access Control APIs
Other APIs
Enterprise Security Group APIs
Firewall Status APIs
Data Types
Error Codes
Tencent Cloud EdgeOne
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
Cloud Workload Protection Platform
History
Introduction
API Category
Asset Management APIs
Virus Scanning APIs
Abnormal Log-in APIs
Password Cracking APIs
Malicious Request APIs
High-Risk Command APIs
Local Privilege Escalation APIs
Reverse Shell APIs
Vulnerability Management APIs
New Baseline Management APIs
Baseline Management APIs
Advanced Defense APIs
Security Operation APIs
Expert Service APIs
Other APIs
Overview Statistics APIs
Settings Center APIs
Making API Requests
Intrusion Detection APIs
Data Types
Error Codes
Key Management Service
History
Introduction
API Category
Key APIs
Making API Requests
Asymmetric Key APIs
Data Types
Error Codes
Secrets Manager
History
Introduction
API Category
Making API Requests
Data Security APIs
Other APIs
Data Types
Error Codes
Captcha
History
Introduction
API Category
Making API Requests
Server APIs
Error Codes
Customer Identity and Access Management
History
Introduction
API Category
Making API Requests
User Management APIs
Data Sync APIs
Audit Management APIs
Data Types
Error Codes
Security Token Service
History
Introduction
API Category
Making API Requests
STS APIs
Data Types
Error Codes
SSL Certificates
History
Introduction
API Category
Making API Requests
Certificate APIs
Certificate Renewal (Certificate ID Unchanged) APIs
CSR APIs
Data Types
Error Codes
Private DNS
History
Introduction
API Category
Making API Requests
Private DNS APIs
Data Types
Error Codes
DNSPod
History
Introduction
API Category
Making API Requests
Line APIs
Package and Value-Added Service APIs
Batch Operation APIs
Group APIs
Record APIs
DNS Query Volume APIs
Alias APIs
Domain APIs
Data Types
Error Codes
Elastic MapReduce
History
Introduction
API Category
Cluster Resource Management APIs
Cluster Services APIs
User Management APIs
Data Inquiry APIs
Scaling APIs
Configuration APIs
Other APIs
Serverless HBase APIs
YARN Resource Scheduling APIs
Making API Requests
Data Types
Error Codes
Elasticsearch Service
History
Introduction
API Category
Instance APIs
Making API Requests
Data Types
Error Codes
Data Lake Compute
History
Introduction
API Category
Making API Requests
Data Table APIs
Task APIs
Metadata APIs
Service Configuration APIs
Permission Management APIs
Database APIs
Data Source Connection APIs
Data Optimization APIs
Data Engine APIs
Resource Group for the Standard Engine APIs
Data Types
Error Codes
Face Recognition
History
Introduction
API Category
Making API Requests
Face Detection and Analysis APIs
Facial Feature Localization APIs
Face Comparison APIs
Group Management APIs
Face Search APIs
Face Verification APIs
Image-based Liveness Detection (High Precision) APIs
Data Types
Error Codes
eKYC
History
Introduction
API Category
Making API Requests
Selfie Verification (Pure API) APIs
Selfie Verification (App SDK) APIs
Identity Verification (App SDK) APIs
Identity Verification(Mobile HTML5) APIs
AI Face Shield (Pure API) APIs
Other APIs
Data Types
Error Codes
Text To Speech
History
Introduction
API Category
Making API Requests
General Text-to-Speech APIs
Data Types
Error Codes
Tencent Machine Translation
History
Introduction
API Category
Making API Requests
APIs
Error Codes
Optical Character Recognition
History
Introduction
API Category
Making API Requests
Document Intelligent APIs
Card and Document OCR APIs
General Text OCR APIs
Vehicle Scene OCR APIs
Data Types
Error Codes
IoT Hub
History
Introduction
API Category
Making API Requests
Device Shadow APIs
Device APIs
CA Certificate APIs
Product APIs
Data Types
Error Codes
TDMQ for CKafka
History
Introduction
API Category
Making API Requests
Other APIs
ACL APIs
Instance APIs
Routing APIs
DataHub APIs
Topic APIs
Data Types
Error Codes
Cloud Message Queue
History
API Category
Making API Requests
Topic APIs
Queue APIs
Introduction
Data Types
Error Codes
Chat
JavaScript
Android
iOS & macOS
Swift
Flutter
Electron
Unity
React Native
C APIs
C++
Short Message Service
History
Introduction
API Category
Making API Requests
SMS Mobile Number APIs
SMS Conversion Rate APIs
Status Pull APIs
SMS Statistics APIs
SMS Signature APIs
SMS Delivery APIs
SMS Template APIs
Data Types
Error Codes
SMS Callback APIs
Tencent Push Notification Service
Overview
API Overview
Call Method
Push APIs
Tag APIs
Account APIs
Statistics APIs
User Attribute APIs
Server-Side Error Codes
Server SDKs
API (Java)
Simple Email Service
History
Introduction
API Category
Making API Requests
Domain Verification APIs
Mail APIs
Template APIs
Statistics APIs
Sender Address APIs
Blocklist APIs
Sending Status Query APIs
Batch Task APIs
Custom Blocklist APIs
Data Types
Error Codes
Tencent Real-Time Communication
History
Introduction
API Category
Room Management APIs
Stream mixing and relay APIs
On-cloud recording APIs
Data Monitoring APIs
Pull stream Relay Related interface
Web Record APIs
AI Service APIs
Cloud Slicing APIs
Cloud Moderation APIs
Making API Requests
Call Quality Monitoring APIs
Usage Statistics APIs
Data Types
Appendix
Error Codes
StreamLive
History
Introduction
API Category
Making API Requests
Input Management APIs
Input Security Group Management APIs
Channel Management APIs
Plan APIs
Watermark Management APIs
Statistics APIs
Data Types
Error Codes
StreamPackage
History
Introduction
API Category
Making API Requests
Channel Management APIs
Advertising Insertion Configuration Management APIs
Channel linear assembly management APIs
VOD remux task APIs
Usage Query APIs
HarvestJob Management APIs
Data Types
Error Codes
StreamLink
History
API Category
Making API Requests
Flow APIs
Data Types
Error Codes
Cloud Streaming Services
History
Introduction
API Category
Making API Requests
Live Pad APIs
Live Stream Mix APIs
Time Shifting APIs
Monitoring Data Query APIs
Billing Data Query APIs
Live Transcoding APIs
Delayed Playback Management APIs
Domain Name Management APIs
Watermark Management APIs
Certificate Management APIs
Stream Pulling APIs
Recording Management APIs
Live Callback APIs
Screencapturing and Porn Detection APIs
Authentication Management APIs
Live Stream Management APIs
Data Types
Error Codes
Video on Demand
History
Introduction
API Category
Other APIs
Media Processing APIs
Task Management APIs
Media Upload APIs
Media Management APIs
Event Notification Relevant API
Media Categorization APIs
Domain Name Management APIs
Distribution APIs
AI-based Sample Management APIs
Region Management APIs
Data Statistics APIs
Carousel-Related APIs
Just In Time Transcode APIs
No longer recommended APIs
Making API Requests
AI-based image processing APIs
Parameter Template APIs
Task Flow APIs
Data Types
Error Codes
Video on Demand API 2024-07-18
Media Processing Service
History
Introduction
API Category
Making API Requests
Processing Task Initiation APIs
Task Management APIs
Transcoding and Enhancement Template APIs
Watermark Template APIs
Screenshot Template APIs
Media AI Template APIs
Media AI—Hotword Lexicon APIs
Media AI—Sample Management APIs
Media Quality Inspection Template APIs
Live Streaming Recording Template APIs
Orchestration Management APIs
Data Statistics APIs
StreamLink—Security Group Management APIs
Other APIs
Image Processing Template APIs
AI Generation APIs
Other APIs
Data Types
Error Codes
Cloud Application Rendering
History
Introduction
API Category
Making API Requests
User APIs
Application Management APIs
Project Management APIs
Concurrency Management APIs
Stream Push Service APIs
Data Types
Error Codes
Game Multimedia Engine
History
Introduction
API Category
Usage APIs
Recording APIs
Making API Requests
Voice Chat APIs
Application APIs
Data Types
Error Codes
Tag
History
Introduction
API Category
Making API Requests
Write APIs
Read APIs
Project APIs
Data Types
Error Codes
Cloud Access Management
History
Introduction
API Category
Making API Requests
User APIs
Policy APIs
Role APIs
Identity Provider APIs
Data Types
Error Codes
CloudAudit
History
Introduction
API Category
Calling Method
CloudAudit APIs
Data Types
Error Codes
Tencent Cloud Organization
History
Introduction
API Category
Making API Requests
Organization Settings APIs
Department and Member Management APIs
Unified Member Login APIs
Member Access Management APIs
Organization Service Management APIs
Organization Management Policy APIs
Resource Sharing APIs
Identity Center Management APIs
Identity Center User Management APIs
Identity Center User Group Management APIs
Identity Center Management SCIM Synchronization APIs
Identity Center Single Sign-On Management APIs
Identity Center Permission Configuration Management APIs
Identity Center Multi-Account Authorization Management APIs
Identity Center Sub-User Synchronization Management APIs
Data Types
Error Codes
TCO API 2018-12-25
Tencent Cloud Observability Platform
History
Introduction
API Category
Making API Requests
Monitoring Data Query APIs
Alarm APIs
Legacy Alert APIs
Notification Template APIs
TMP APIs
Grafana Service APIs
Event Center APIs
TencentCloud Managed Service for Prometheus APIs
Monitoring APIs
Data Types
Error Codes
Real User Monitoring
History
Introduction
API Category
Making API Requests
Console APIs
Business System and Project Information APIs
Custom Speed Test APIs
Custom Event APIs
API Monitoring APIs
Exception Analysis APIs
Page View APIs
Static Resource Monitoring APIs
Log APIs
Page Performance APIs
Data Types
Error Codes
International Partners
History
Introduction
API Category
Making API Requests
Customer Management APIs
Credit Management APIs
Agent APIs
Bill Management APIs
Voucher Management APIs
Commission Management APIs
Data Types
Error Codes
Billing Center
API Category
Funds Management APIs
Order Management APIs
Resource Management APIs
Bill Management APIs
Cost Allocation Management APIs
Cost Management APIs
Making API Requests
Organization Account APIs
Data Types
Error Codes
TDSQL Boundless
History
Introduction
API Category
Making API Requests
Instance APIs
Security Group APIs
Task APIs
Backup APIs
Rollback APIs
Parameter APIs
Database APIs
Data Types
Error Codes
TDMQ for MQTT
History
Introduction
API Category
Making API Requests
Cluster APIs
Topic APIs
Authorization Policy APIs
User APIs
Client APIs
Message APIs
Message Enhancement Rule APIs
Data Types
Error Codes
Tencent HY
History
Introduction
API Category
Making API Requests
Hunyuan Text APIs
Hunyuan 3D APIs
Data Types
Error Codes
Smart Media Hosting
History
Introduction
API Category
Making API Requests
PaaS Service APIs
Official Cloud Disk APIs
Data Types
Error Codes
Quota Center
History
Introduction
API Category
Making API Requests
Alarm APIs
Data Types
Error Codes
Message Center
History
Introduction
API Category
Making API Requests
Message Subscription APIs
Data Types
Error Codes
Business Intelligence
History
Introduction
API Category
Making API Requests
Project Management APIs
Role APIs
Database Table APIs
Report Embedding APIs
Page Management APIs
Data Types
Error Codes
LLM Knowledge Engine Basic API
History
Introduction
API Category
Making API Requests
Atomic Capability APIs
Data Types
Error Codes
Tencent Cloud Agent Development Platform
History
API Category
Making API Requests
Atomic Capability APIs
Operation Optimization APIs
Document Library APIs
Q&A Database APIs
Knowledge Tag APIs
Application Management APIs
Enterprise Management APIs
Billing APIs
Release Management APIs
Dialogue Endpoint APIs
Data Statistics APIs
Data Types
Error Codes
Tencent Cloud Blockchain as a Service
History
Introduction
API Category
Making API Requests
Hyperledger Fabric 2.3 APIs
Data Types
Error Codes
Performance Testing Service
History
Introduction
API Category
Making API Requests
PTS-related APIs
Data Types
Error Codes
Real-time Teleoperation
History
Introduction
API Category
Making API Requests
Project APIs
Device APIs
Session APIs
Authorization APIs
Other APIs
Data Types
Error Codes
Gateway Load Balancer
History
Introduction
API Category
Making API Requests
Target Group APIs
GWLB APIs
Other APIs
Data Types
Error Codes
Identity Aware Platform
History
Introduction
API Category
Making API Requests
IAP APIs
Error Codes
Cloud Dedicated Cluster
History
Introduction
API Category
Making API Requests
Cloud Dedicated Cluster (CDC) APIs
Data Types
Error Codes
Image Creation Large Model
History
Introduction
API Category
Making API Requests
Image Style Transfer APIs
Data Types
Error Codes
Face Fusion
API Category
Making API Requests
Image Face Fusion (Basic) APIs
Video Face Fusion (Single Face) APIs
Data Types
Error Codes
Tencent Smart Advisor-Chaotic Fault Generator
History
Introduction
API Category
Making API Requests
Task APIs
Template Library APIs
Data Types
Error Codes
Tencent HealthCare Omics Platform
History
Introduction
API Category
Making API Requests
Environment Management APIs
Tencent Healthcare Omics Platform APIs
Data Types
Error Codes
Tencent Cloud TCHouse-D
History
Introduction
API Category
Making API Requests
Cluster Operation APIs
Database and Table APIs
Cluster Information Viewing APIs
Hot-Cold Data Layering APIs
Database and Operation Audit APIs
User and Permission APIs
Resource Group Management APIs
Data Types
Error Codes
Tencent Cloud WeData
History
Introduction
API Category
Making API Requests
Project Management APIs
Smart Ops Related Interfaces
Resource Group APIs
Data Development APIs
Data Asset - Data Dictionary APIs
Data Development APIs
Ops Center APIs
Data Exploration APIs
Data Operations Related Interfaces
Asset APIs
Metadata Related Interfaces
Task Operations APIs
Data Security APIs
Instance Operation and Maintenance Related Interfaces
Data Map and Data Dictionary APIs
Data Quality Related Interfaces
DataInLong APIs
Platform Management APIs
Data Source Management APIs
Data Quality APIs
Platform Management APIs
Asset Data APIs
Data Source Management APIs
Data Types
Error Codes
WeData API 2025-08-06
Anti-DDoS
History
Introduction
API Category
Making API Requests
Anti-DDoS Advanced Instance APIs
Resource List APIs
Protection Configuration APIs
Other APIs
Alarm Notification APIs
Connection Configuration APIs
Intelligent Scheduling APIs
Black hole unblocking APIs
Statistical Report APIs
Data Types
Error Codes
Cloud Contact Center
History
Introduction
API Category
Making API Requests
Agent APIs
Skill Group APIs
Number APIs
Dual Call APIs
Predictive Outbound Call APIs
SIP Phone APIs
Call Service Record APIs
Billing APIs
Other APIs
Outbound Call APIs
Speech Intelligent Agent APIs
Data Types
Error Codes
Tencent Cloud Super App as a Service
History
Introduction
API Category
Making API Requests
Operation Management APIs
Platform Management APIs
Sensitive API-Related APIs
Role Management APIs
Team Management APIs
Other Console APIs
Mini Program or Mini Game APIs
Management-Sensitive APIs
Global Domain Management APIs
Superapp APIs
User Management APIs
Data Types
Tencent Cloud Smart Advisor
History
Introduction
API Category
Making API Requests
Other APIs
Task APIs
Cloud Architecture Console APIs
Data Types
Error Codes
TDMQ for RabbitMQ
History
Introduction
API Category
Making API Requests
Relevant APIs for RabbitMQ Serverless PAAS Capacity
RabbitMQ Serverless Instance Management APIs
Data Types
Error Codes
Control Center
History
Introduction
API Category
Making API Requests
Account Factory APIs
Data Types
Error Codes
TDMQ for CMQ
API Documentation
API 2.0 to 3.0 Switch Guide
Tencent Cloud TCHouse-P
History
Introduction
API Category
Making API Requests
Information Query APIs
Instance APIs
Query APIs
Cluster Management APIs
Cluster Operation APIs
Data Types
Error Codes
TDMQ for RocketMQ
History
API Category
Making API Requests
Topic APIs
Consumer Group APIs
Message APIs
Role Authentication APIs
Hitless Migration APIs
Cloud Migration APIs
Cluster APIs
Data Types
Error Codes
Cloud Dedicated Zone
History
Introduction
API Category
Making API Requests
Availability Zone APIs
Data Types
Error Codes
Tencent Cloud Health Dashboard
History
Introduction
API Category
Making API Requests
Event APIs
Data Types
Error Codes
Application Performance Management
History
Introduction
API Category
Making API Requests
Application APIs
Business System APIs
General Query APIs
Unavailable APIs
Performance Analysis APIs
Data Types
Error Codes
Config
History
Introduction
API Category
Making API Requests
Rule APIs
Resource APIs
Data Types
Error Codes
Automatic Speech Recognition
History
Introduction
API Category
Making API Requests
Recording Recognition APIs
Real-Time Speech Recognition APIs
Data Types
Error Codes
Tencent Cloud TI Platform
History
Introduction
API Category
Making API Requests
Online Service APIs
Data Types
Error Codes
Web Application Firewall
History
Introduction
API Category
Making API Requests
Asset Management APIs
Billing APIs
Protection Settings APIs
Other APIs
IP Management APIs
Integration APIs
Log Service APIs
Security Overview APIs
Rule Engine APIs
Data Types
Error Codes
Cloud Security Center
History
Introduction
API Category
Making API Requests
Multi-account management related APIs
Scan Task APIs
Risk Center APIs
Asset Center APIs
Cloud Boundary Analysis APIs
Cloud API Anomaly Detection APIs
Report Download APIs
Solid Protection APIs
Cloud Security Center Overview APIs
Data Types
Error Codes
Risk Control Engine
History
Introduction
API Category
Making API Requests
TencentCloud API APIs
Data Types
Error Codes
TencentDB for CTSDB
History
Introduction
API Category
Making API Requests
Instance APIs
Database APIs
Data Types
Error Codes
Tencent Interactive Whiteboard
History
Introduction
API Category
Making API Requests
Whiteboard Push APIs
Other APIs
Document Transcoding APIs
Real-Time Recording APIs
Statistics Query APIs
Whiteboard Snapshot APIs
Recording Video Generation APIs
Data Types
Error Codes
Tencent Container Security Service
History
Introduction
API Category
Making API Requests
Network Security APIs
Cluster Security APIs
Security Compliance APIs
Runtime security - High-risk syscalls
Runtime Security - Reverse Shell APIs
Runtime Security APIs
Alert Settings APIs
Advanced prevention - K8s API abnormal requests
Asset Management APIs
Security Operations - Log Analysis APIs
Runtime Security - Trojan Call APIs
Runtime Security - Container Escape APIs
Image Security APIs
Billing APIs
Data Types
Error Codes
Domains
History
Introduction
API Category
Making API Requests
Domain Management APIs
Domain Query APIs
Bulk Operation APIs
Registrant Profile APIs
Other APIs
Data Types
Error Codes
Low-code Interactive Classroom
History
Introduction
API Category
Making API Requests
User Login APIs
Room Management APIs
Group Management APIs
Application Configuration APIs
Recording Management APIs
Courseware Management APIs
User Management APIs
Developer APIs
Data Types
Error Codes

CreateExporterIntegration

Modo Foco
Tamanho da Fonte
Última atualização: 2026-03-26 22:27:28

1. API Description

Domain name for API request: monitor.intl.tencentcloudapi.com.

Create an exporter integration in the integration center. Due to the considerable number of integrations, it is advisable to create through the console. Prerequisite: Authorized to create a managed EKS cluster. Verification method: 1. Confirm on the console interface. If no authorization notification appears, it indicates authorization is granted. 2. Query the cluster status via the DescribePrometheusInstanceInitStatus API. If the managed cluster does not exist, create it using the RunPrometheusInstance API.

A maximum of 20 requests can be initiated per second for this API.

We recommend you to use API Explorer
Try it
API Explorer provides a range of capabilities, including online call, signature authentication, SDK code generation, and API quick search. It enables you to view the request, response, and auto-generated examples.

2. Input Parameters

The following request parameter list only provides API request parameters and some common parameters. For the complete common parameter list, see Common Request Parameters.

Parameter Name Required Type Description
Action Yes String Common Params. The value used for this API: CreateExporterIntegration.
Version Yes String Common Params. The value used for this API: 2018-07-24.
Region Yes String Common Params. For more information, please see the list of regions supported by the product. This API only supports: ap-bangkok, ap-beijing, ap-chengdu, ap-chongqing, ap-guangzhou, ap-hongkong, ap-jakarta, ap-nanjing, ap-seoul, ap-shanghai, ap-shanghai-fsi, ap-shenzhen-fsi, ap-singapore, ap-tokyo, eu-frankfurt, na-ashburn, na-siliconvalley, sa-saopaulo.
InstanceId Yes String Instance ID
Kind Yes String Type (obtain through the DescribePrometheusIntegrations api, using the ExporterType field of each item).
Content Yes String Integrated configuration
KubeType No Integer Kubernetes cluster type, optional, valid values are as follows:.
  • 1 = TKE
  • 2 = EKS
  • 3 = MEKS
  • ClusterId No String Cluster ID, optional.

    3. Output Parameters

    Parameter Name Type Description
    Names Array of String The list of successfully created integrations.
    RequestId String The unique request ID, generated by the server, will be returned for every request (if the request fails to reach the server for other reasons, the request will not obtain a RequestId). RequestId is required for locating a problem.

    4. Example

    Example1 a. Creating a Cloud Monitor Integration

    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as qcloud-exporter and required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as qcloud-exporter
      3.3. spec.instanceSpec.region is the region where the Cloud Product is located, required. For example, to collect Cloud services in the Guangzhou region, you can set to Guangzhou or ap-guangzhou. This parameter will be converted to the label of the object, named instance-region.
      3.4. spec.instanceSpec.delaySeconds indicates the data collection delay. It is an integer in seconds and can be left blank. The default value 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 in integration. When the value is >0, the data point will retain the original timestamp, and the data will inevitably be delayed by the set time.
      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 to cloud product instances or modifications to cloud Tags will be reflected in metrics after an instance refresh, with a wait time of up to one instance refresh interval.
      3.6. spec.instanceSpec.useRole indicates whether to use a service role, boolean type, required. The current logic always uses a service role, therefore required true.
      3.7. spec.instanceSpec.labels Used to add custom tags to metrics, key-value pair type, optional
      3.8. spec.instanceSpec.restart is used for restarting integration or updating the integration version in terraform. It can be an integer or a unix second-level timestamp. Optional.
      3.9. spec.exporterSpec.[Cloud Product] indicates whether to collect data from the corresponding cloud services. It is a boolean type, where true means collecting data from the cloud service. The meanings of cloud service codes are as follows: cvm: Cloud Virtual Machine, sdn_vm: Cloud Virtual Machine (private network), 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: database MySQL (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 dedicated line, dcx: Direct Connect - dedicated tunnel, dcg: Direct Connect - Direct Connect gateway, lighthouse: 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. For more code meanings, please refer to the Cloud Monitoring Integration Guide.
      3.10. 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/87398?from_cn_redirect=1#29fe272b-ac9e-4932-b6dc-972c2b1ef9dc).

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "qcloud-exporter",
        "Content": "{\"name\":\"test-qcloud\",\"kind\":\"qcloud-exporter\",\"spec\":{\"instanceSpec\":{\"region\":\"Guangzhou\",\"delaySeconds\":0,\"reload_interval_minutes\":10,\"useRole\":true,\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"},\"restart\":1770373080},\"exporterSpec\":{\"cvm\":true,\"cbs\":true},\"scrapeSpec\":{\"relabelConfigs\":\"metric_relabel_configs:\\n- action: labeldrop\\n  regex: tmp_test_label\\n\"}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "test-qcloud"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example2 b. Creating a CVM Node Exporter Integration

    The integration requires the CVM instance and the Prometheus instance to be connected via the private network (for example, in the same VPC), and the CVM instance must have the tencent cloud Automation Tools (https://www.tencentcloud.com/document/product/1340/51945?from_cn_redirect=1) installed.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as cvm-node-exporter-sd and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. kind is the integration type, required and fixed as cvm-node-exporter-sd here
      3.2. spec.job is the scrape configuration, required, in yaml format. For reference input, see the example. Among them, instance_ids can fill in multiple CVM instance ids.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "cvm-node-exporter-sd",
        "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\"}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "node-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example3 c. Creating a CVM Integration

    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as cvm-http-sd-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. kind is the integration type, required and fixed as cvm-http-sd-exporter
      3.2. spec.job is the scrape configuration, required, in yaml format. For specific configuration, see scraping configuration instructions

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "cvm-http-sd-exporter",
        "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:ExampleTagKey\\n    values: \\n    - ExampleTagValue\\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\"}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "example-job-name"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example4 d. Creating a Health Check Integration

    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as blackbox-exporter and required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as blackbox-exporter
      3.3. spec.instanceSpec.module is the detection method, required. Available values are http_get, http_post, tcp, ssh, ping.
      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.
      3.5. spec.instanceSpec.noAllowRedirect controls whether redirection is forbidden. It is a boolean type and optional, only applicable to the detection methods http_get and http_post. true means redirection is forbidden, and it can be left blank directly. It defaults to false.
      3.6. spec.instanceSpec.insecureSkipVerify controls whether to disable target certificate verification. It is of boolean type and optional, only applicable to the http_get and http_post detection methods. Setting it to true indicates that it is disabled. You can leave it blank as it defaults to false.
      3.7. spec.instanceSpec.headers is used to add headers when probing the target. It is in key-value pair format, optional, and only applicable to the detection methods http_get and http_post.
      3.8. spec.instanceSpec.labels Used to add custom tags to metrics, key-value pair type, optional
      3.9. spec.scrapeSpec.interval is used for custom check interval, optional, 15s is selected by default

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "blackbox-exporter",
        "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\"}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "test-blackbox"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example5 e. Creating an Ingress Nginx Controller Integration

    Collect Ingress NGINX Controller in the associated cluster.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as nginx-ingress and is required.
    3. ClusterId is the cluster ID associated with the Prometheus instance where Ingress NGINX Controller is deployed, required.
    4. KubeType is the cluster type corresponding to ClusterId and is required. 1 means tke cluster, and 2 or 3 means eks cluster.
    5. The parameter format of Content is as shown in the example. The details are as follows:
      5.1. kind is the integration type, required and fixed as nginx-ingress here
      5.2. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      5.3. spec.instanceSpec.namespace is the namespace where the Ingress NGINX Controller resides, required
      5.4. spec.instanceSpec.name is the name of the Ingress NGINX Controller and is required. Use the name of the Deployment or DaemonSet.
      5.5. spec.instanceSpec.workload is the cluster object type of Ingress NGINX Controller, required, such as deployment or daemonset.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "ClusterId": "cls-test",
        "KubeType": 1,
        "Kind": "nginx-ingress",
        "Content": "{\"kind\":\"nginx-ingress\",\"name\":\"ingress-test\",\"spec\":{\"instanceSpec\":{\"namespace\":\"namespace\",\"name\":\"controller-name\",\"workLoad\":\"deployment\"}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "ingress-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example6 f. Creating a Cdwch Integration

    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as cdwch-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. kind is the integration type, required and fixed as cdwch-exporter
      3.2. spec.job is the scrape configuration, required in yaml format. For reference, see the input example. You only need to modify the task name and instance ID.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "cdwch-exporter",
        "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\"}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "cdwch-example-job"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example7 g. Creating an EMR Integration

    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as emr-exporter and required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      4.1. kind is the integration type, required and fixed as emr-exporter here
      4.2. spec.job is the scrape configuration, required, in yaml format. For details, see the EMR integration guide

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "emr-exporter",
        "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\"}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "emr-example-job"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example8 h. Creating a Scrape Task

    Install a no-auth agent to access the native API of Prometheus over the private network without authentication.
    Once created, you can call the DescribeExporterIntegrations API to get the integrated private IP address:Port through the InstanceDesc parameter. This address can replace the Prometheus instance address for authentication access.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as raw-job, required
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. kind is the integration type, required and fixed as raw-job here
      3.2. spec.spec.job is the native Prometheus scrape configuration, required, in yaml format. For configuration instructions, see configuration document.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "raw-job",
        "Content": "{\"kind\":\"raw-job\",\"spec\":{\"job\":\"job_name: test-job\\nscrape_interval: 30s\\nstatic_configs:\\n- targets:\\n  - 127.0.0.1:9090\"}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "test-job"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example9 i. Creating a Consul Integration

    Install Consul Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as consul-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as consul-exporter here
      3.3. spec.instanceSpec.server is the address of the Consul instance, required.
      3.4. spec.instanceSpec.labels is used to add custom Tags for metrics, in key-value pair format, optional.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "consul-exporter",
        "Content": "{\"name\":\"consul-test\",\"kind\":\"consul-exporter\",\"spec\":{\"instanceSpec\":{\"server\":\"1.1.1.1:8080\",\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "consul-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example10 j. Creating an Elasticsearch Integration

    Install ElasticSearch Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as es-exporter and required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as es-exporter
      3.3. spec.instanceSpec.user is the username of ElasticSearch, required
      3.4. spec.instanceSpec.password is the password of ElasticSearch, required
      3.5. spec.instanceSpec.url is the ElasticSearch address, required
      3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional.
      3.7. spec.exporterSpec.all indicates whether to query statistical information for all nodes in a cluster. It is a boolean type and optional. The default value is false. If false, it only queries statistical information for the connected node.
      3.8. spec.exporterSpec.indices indicates whether to query index statistics for all in a cluster. It is of boolean type, optional, and the default value is false.
      3.9. spec.exporterSpec.indicesSettings indicates whether to query statistical information of all index configurations in a cluster. It is of boolean type, optional, and the default value is false.
      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.
      3.11. spec.exporterSpec.snapshots indicates whether to query the snapshot statistical information of the cluster. It is a boolean type, optional, and the default value is false.
      3.12. spec.exporterSpec.clusterSettings indicates whether to query cluster configuration statistical information, boolean type, optional, default value is false

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "es-exporter",
        "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}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "es-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example11 k. Creating a Kafka Integration

    Install kafka Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as kafka-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as kafka-exporter
      3.3. spec.instanceSpec.servers is the address of the Kafka instance, required. You can fill in more than one. We recommend one integration per instance.
      3.4. spec.instanceSpec.version is the version of the Kafka instance. It is optional, but an error will be reported if not filled in for some versions, such as 0.10.2.0.
      3.5. spec.instanceSpec.labels is used to add custom tags to metrics. It is of key-value pair type and optional.
      3.6. spec.exporterSpec.topicFilter is for filtering topics. It is optional and defaults to collecting all. Fill in regular expression to collect only eligible topics.
      3.7. spec.exporterSpec.groupFilter is for filtering groups and can be left blank. By default, all groups are collected. After filling in regular expression, only eligible groups are collected.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "kafka-exporter",
        "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.*\"}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "kafka-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example12 l. Creating a RocketMQ Integration

    Install RocketMQ Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as rocketmq-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as rocketmq-exporter
      3.3. spec.instanceSpec.address is the domain names or IP addresses of the RocketMQ instance, required. You can fill in more than one, separate them with semicolons.
      3.4. spec.instanceSpec.version is the version of the RocketMQ instance, required, such as V4_9_4
      3.5. spec.instanceSpec.labels is used to add custom tags to metrics, key-value pair type, optional.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "rocketmq-exporter",
        "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\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "rocketmq-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example13 m. Creating a Memcached Integration

    Install Memcached Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as memcached-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as memcached-exporter
      3.3. spec.instanceSpec.address is the domain names or IP addresses of the Memcached instance, required
      3.4. spec.instanceSpec.labels is used to add custom Tags for metrics, in key-value pair format, optional.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "memcached-exporter",
        "Content": "{\"name\":\"memcached-test\",\"kind\":\"memcached-exporter\",\"spec\":{\"instanceSpec\":{\"address\":\"127.0.0.1:8080\",\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "memcached-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example14 n. Creating a MongoDB Integration

    Install MongoDB Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as mongodb-exporter and required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as mongodb-exporter
      3.3. spec.instanceSpec.user is the username of the MongoDB instance, required
      3.4. spec.instanceSpec.password is the password of the MongoDB instance, required
      3.5. spec.instanceSpec.servers is the connection address of the MongoDB instance, required, you can fill in more than one, separate with commas
      3.6. spec.instanceSpec.labels is used to add custom tags to metrics, with key-value pair type, optional.
      3.7. spec.exporterSpec.collectors is the collection configuration of the exporter, optional, an array of strings. The example shows all fillable 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, and connpoolstats means enabling the collection of connection pool statistics.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "mongodb-exporter",
        "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\"]}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "mongodb-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example15 o. Creating a MySQL Integration

    Install MySQL Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as mysql-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as mysql-exporter
      3.3. spec.instanceSpec.user is the username of the MySQL instance, required
      3.4. spec.instanceSpec.password is the password of the MySQL instance, required.
      3.5. spec.instanceSpec.address is the connection address of the MySQL instance, required
      3.6. spec.instanceSpec.labels is used to add custom tags to metrics, key-value pair type, optional

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "mysql-exporter",
        "Content": "{\"name\":\"mysql-test\",\"kind\":\"mysql-exporter\",\"spec\":{\"instanceSpec\":{\"user\":\"root\",\"password\":\"password\",\"address\":\"127.0.0.1:8080\",\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "mysql-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example16 p. Creating a PostgreSQL Integration

    Install PostgreSQL Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as postgres-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as postgres-exporter here
      3.3. spec.instanceSpec.user is the username of the PostgreSQL instance, required
      3.4. spec.instanceSpec.password is the password of the PostgreSQL instance, required
      3.5. spec.instanceSpec.address is the connection address of the PostgreSQL instance, required
      3.6. spec.instanceSpec.labels is used to add custom tags to metrics, key-value pair type, optional

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "postgres-exporter",
        "Content": "{\"name\":\"postgresql-test\",\"kind\":\"postgres-exporter\",\"spec\":{\"instanceSpec\":{\"user\":\"user\",\"password\":\"password\",\"address\":\"127.0.0.1:8080\",\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "postgresql-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example17 q. Creating a Redis Integration

    Install Redis Exporter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as redis-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as redis-exporter
      3.3. spec.instanceSpec.address is the connection address of the Redis instance, required
      3.4. spec.instanceSpec.password is the password of the Redis instance, required.
      3.5. spec.instanceSpec.labels is used to add custom tags to metrics, key-value pair type, optional.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "redis-exporter",
        "Content": "{\"name\":\"redis-test\",\"kind\":\"redis-exporter\",\"spec\":{\"instanceSpec\":{\"address\":\"127.0.0.1:8080\",\"password\":\"password\",\"labels\":{\"labelKey\":\"labelValue\",\"test\":\"test\"}}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "redis-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example18 r. Creating a Graphite Integration

    Install Graphite Exporter to convert Graphite metrics to Prometheus Metrics.
    Once created, you can call the DescribeExporterIntegrations API to obtain the integrated private IP address:Port host address through the InstanceDesc parameter.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as graphite-exporter and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as graphite-exporter here
      3.3. spec.instanceSpec.isStrictMatch indicates whether to perform a strict match on mappingConfig. This field is optional and the default is false.
      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 Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "graphite-exporter",
        "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}\"}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "graphite-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    Example19 s. Creating a No-Authentication Proxy Integration

    Install a no-auth agent to access the native API of Prometheus over the private network without authentication.
    Once created, you can call the DescribeExporterIntegrations API to get the integrated private IP address:Port through the InstanceDesc parameter. This address can replace the Prometheus instance address for authentication access.
    Parameter description:

    1. InstanceId is the Prometheus Instance ID, required
    2. The Kind parameter is fixed as auth-proxy and is required.
    3. The parameter format of Content is as shown in the example. Details are as follows:
      3.1. name is the integration name, required and globally unique, and must match the regex ^a-z0-9?(.a-z0-9?)*$
      3.2. kind is the integration type, required and fixed as auth-proxy here.
      3.3. spec.instanceSpec.enableSelfMonitor indicates whether to collect self-monitoring metrics. This field is optional and default is false. The self-monitoring metric is auth_proxy_http_requests_total{result=~"success|error"}, where only request quantity with success or failure are counted.

    Input Example

    POST / HTTP/1.1
    Host: monitor.intl.tencentcloudapi.com
    Content-Type: application/json
    X-TC-Action: CreateExporterIntegration
    <Common request parameters>
    
    {
        "InstanceId": "prom-1",
        "Kind": "auth-proxy",
        "Content": "{\"name\":\"auth-test\",\"kind\":\"auth-proxy\",\"spec\":{\"instanceSpec\":{\"enableSelfMonitor\":true}}}"
    }
    

    Output Example

    {
        "Response": {
            "Names": [
                "auth-test"
            ],
            "RequestId": "xyz"
        }
    }
    

    5. Developer Resources

    SDK

    TencentCloud API 3.0 integrates SDKs that support various programming languages to make it easier for you to call APIs.

    Command Line Interface

    6. Error Code

    The following only lists the error codes related to the API business logic. For other error codes, see Common Error Codes.

    Error Code Description
    AuthFailure Error with CAM signature/authentication.
    AuthFailure.UnauthorizedOperation The request is not authorized. For more information on the authentication, see the CAM documentation.
    FailedOperation Operation failed.
    FailedOperation.AccessTKEFail Failed to access the TKE cluster.
    FailedOperation.ClusterNotFound The cluster does not exist.
    FailedOperation.DbQueryFailed Failed to query the database.
    FailedOperation.InstanceNotRunning The instance is not running.
    FailedOperation.ResourceExist The resource already exists.
    FailedOperation.ResourceNotFound The resource does not exist.
    FailedOperation.ResourceOperating The resource is being manipulated.
    FailedOperation.TKEResourceConflict A conflict occurred while updating the TKE resource.
    InternalError Internal error.
    InvalidParameter Invalid parameter.

    Ajuda e Suporte

    Esta página foi útil?

    comentários