Data Multi-Write
This function enables cross-VPC access without exposing server network information. Monitoring data can be reported to self-built Prometheus instances more securely.
Prerequisites
- Your service has been connected to a Prometheus instance for ECS. For details, see Prometheus Instance for ECS.
- Your service has been connected to a Prometheus instance for cloud services. For details, see Prometheus Instance for Cloud Services.
- Your service has been connected to a common Prometheus instance. For details, see Common Prometheus Instance.
- Your service has been connected to a Prometheus instance for CCE. For details, see Prometheus Instance for CCE.
Precautions
- Only the default or common Prometheus instance, and the Prometheus instances for CCE, cloud services, and ECS support data multi-write.
- For Prometheus instances for CCE, the metrics processed using recording rules do not support data multi-write.
- Some default metrics generated by AOM (such as aom_metrics_total, aom_metrics_total_per_hour, ALERTS, and ALERTS_FOR_STATE) do not support data multi-write.
- When the metrics of the default Prometheus instance are dumped using the data multi-write function, the names of some dumped metrics may be inconsistent with those displayed on the AOM page. For example, the names of metrics reported by ICAgent are in lower camel case. These names are converted to the snake case when being displayed on the AOM page. (Example: memUsage is displayed as aom_container_memory_usage.)
Procedure
- Log in to the AOM 2.0 console and choose Prometheus Monitoring > Instances.
- In the Prometheus instance list, click a Prometheus instance that supports data multi-write. The instance details page is displayed.
- In the navigation pane on the left, choose Data Write.
- Set the configuration process.
- Select a VPC endpoint service. Select a VPC endpoint service from the drop-down list.
The selected VPC endpoint service must be in the same VPC as the self-built Prometheus instance. Only VPC endpoint services whose Backend Resource Type is Cloud Server or Elastic Load Balance can be selected.
- Add whitelist permissions.
Click Add Now to add the provided account ID to the VPC endpoint service whitelist.
- Create a VPC endpoint.
- Select a VPC endpoint service. Select a VPC endpoint service from the drop-down list.
- On the VPC endpoint service details page, go to the Connection Management tab page and ensure that the status is Accepted.
- Set a data write address. Table 1 describes the parameters.
Table 1 Data write address parameters Parameter
Description
Self-built Prometheus Instance's Remote Write Address
Remote write address of the self-built Prometheus instance. Set this parameter based on site requirements.
The format is "{IP address:port number}/{path}". Example: 192.168.0.1:9090/api/v1/write
Authentication Mode
Authentication mode for accessing a self-built Prometheus instance.
- Basic: Enter the username and password of the Prometheus instance.
- Token: A token is required for authentication.
- None: No authentication is required.
- Click Save.
Wait for about 5 minutes. You can check the reported metric data in the self-built Prometheus instance.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot