- Product Introduction
- Purchase Guide
- Getting Started
- Integration Guide
- Scrape Configuration Description
- Custom Monitoring
- EMR Integration
- Java Application Integration
- Go Application Integration
- Exporter Integration
- Elasticsearch Exporter Integration
- Kafka Exporter Integration
- MongoDB Exporter Integration
- PostgreSQL Exporter Integration
- Nginx Exporter Integration
- Redis Exporter Integration
- MySQL Exporter Integration
- Consul Exporter Integration
- Memcached Exporter Integration
- Integration with Other Exporters
- CVM Node Exporter
- Apache Exporter Integration
- Health Check
- Instructions for Installing Components in the TKE Cluster
- Cloud Monitoring
- Read Cloud-Hosted Prometheus Instance Data via Remote Read
- Agent Self-Service Access
- Pushgateway Integration
- Security Group Open Description
- Operation Guide
- Practical Tutorial
- Terraform
- FAQs
- Service Level Agreement
- TMP Policy
- Product Introduction
- Purchase Guide
- Getting Started
- Integration Guide
- Scrape Configuration Description
- Custom Monitoring
- EMR Integration
- Java Application Integration
- Go Application Integration
- Exporter Integration
- Elasticsearch Exporter Integration
- Kafka Exporter Integration
- MongoDB Exporter Integration
- PostgreSQL Exporter Integration
- Nginx Exporter Integration
- Redis Exporter Integration
- MySQL Exporter Integration
- Consul Exporter Integration
- Memcached Exporter Integration
- Integration with Other Exporters
- CVM Node Exporter
- Apache Exporter Integration
- Health Check
- Instructions for Installing Components in the TKE Cluster
- Cloud Monitoring
- Read Cloud-Hosted Prometheus Instance Data via Remote Read
- Agent Self-Service Access
- Pushgateway Integration
- Security Group Open Description
- Operation Guide
- Practical Tutorial
- Terraform
- FAQs
- Service Level Agreement
- TMP Policy
1.INTRODUCTION
This Module applies if you use the Prometheus Monitoring Service (TMP) (“Feature”). This Module is incorporated into the privacy policy located at Privacy Policy. Terms used but not defined in this Module shall have the meaning given to them in the Privacy Policy. In the event of any conflict between the Privacy Policy and this Module, this Module shall apply to the extent of the inconsistency.
2.CONTROLLERSHIP
The controller of the personal information described in this Module is as specified in the Privacy Policy.
3.AVAILABILITY
This Feature is available to users globally but primarily intended for users located in Singapore and Frankfurt.
4.HOW WE USE PERSONAL INFORMATION
We will use the information in the following ways and in accordance with the following legal bases:
Personal Information | Use | Legal Basis |
Service Operational Data (as provided by you): IP or domain: the IP or domain of the object to be captured by the Feature URL: address URL Instance (i.e. the instance where you use the Feature) information: region, specifications | We process this data for the purposes of providing the Feature to you. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
Log Data: Request exception log (i.e. a log created in the event of an issue in service delivery) User operation log of console, including APPID, action, timestamp, UIN | We use this information to ensure the Feature functions as required, including for troubleshooting and maintenance. | We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
5.HOW WE STORE AND SHARE PERSONAL INFORMATION
As specified in the Privacy Policy. Additionally, your APPID and UIN is stored and backed up in TencentDB for MySQL and will be retained for as long as you use the Feature. When your use of the Feature is terminated, we will delete this data automatically within seven days after termination.
6.DATA RETENTION
We will retain personal information in accordance with the following:
Personal Information | Retention Policy |
Service Operational Data | We retain such data until you no longer use or delete the Feature, or request for deletion, upon which such data will be deleted automatically within seven days. |
Log Data | We retain such data until the earlier of 180 days after collection, after which it is automatically deleted within seven days, or until you request for deletion, upon which such data will be deleted immediately. |
Yes
No
Was this page helpful?