- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- 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
- Health Check
- Cloud Monitoring
- Read Cloud-Hosted Prometheus Instance Data via Remote Read
- FAQs
- Service Agreement
- TMP Policy
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Practical Tutorial
- 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
- Health Check
- Cloud Monitoring
- Read Cloud-Hosted Prometheus Instance Data via Remote Read
- FAQs
- Service Agreement
- TMP Policy
1. BACKGROUND
This Module applies if you the Prometheus Monitoring Service (TMP) (“Feature”). This Module is incorporated into the Data Privacy and Security Agreement located at DPSA. Terms used but not defined in this Module shall have the meaning given to them in the DPSA. In the event of any conflict between the DPSA and this Module, this Module shall apply to the extent of the inconsistency.
2. PROCESSING
We will process the following data in connection with the Feature:
Personal Information | Use |
Configuration Data: Configuration settings (where you use the agent function, you will need to enter the configuration data including the IP of the captured object and the address required for data reporting) Alarm configuration data (you can set alarm rules (e.g. traffic reminders and abnormality reminders) and define what circumstances will trigger the alarm) | The purpose of collecting the configuration settings is to provide you with the Feature by capturing user-reported data. The purpose of collecting the alarm configuration data is to provide you with the alert service. |
Monitoring Data:
Data being captured by you and analysed through the Feature, including the aggregated data processed and stored by you | We only process the data for the purposes of providing the Feature to you and ensuring it fulfills your customized requirements for processing and analyzing your business-related data. |
3. SERVICE REGION
As specified in the DPSA.
4. SUB-PROCESSORS
As specified in the DPSA.
5. DATA RETENTION
We will store personal data processed in connection with the Feature as follows:
Personal Information | Retention Policy |
Configuration Data Monitoring Data | Stored in accordance with the storage time selected by you, i.e. either 15, 30 or 45 days. Once the time period reaches the selected storage time, such data will be deleted automatically within seven days. If you request to delete the data prior to the expiry of the selected storage time, such data will be deleted immediately. |
You can request deletion of such personal data in accordance with the DPSA.
6. SPECIAL CONDITIONS
You must ensure that this Feature is only used by end users who are of at least the minimum age at which an individual can consent to the processing of their personal data. This may be different depending on the jurisdiction in which an end user is located.
Yes
No
Was this page helpful?