Help Center/
Application Operations Management/
FAQs (2.0)/
Infrastructure Monitoring/
Why Can't AOM Detect Workloads After the Pod YAML File Is Deployed Using Helm?
Updated on 2024-09-06 GMT+08:00
Why Can't AOM Detect Workloads After the Pod YAML File Is Deployed Using Helm?
Symptom
After the pod YAML file is deployed using Helm, AOM cannot detect workloads.
Possible Cause
Compare the YAML file deployed using Helm with that deployed on the CCE console. Environment parameters are found missing in the file deployed using Helm.
Figure 1 Comparing YAML files
Solution
- Log in to the CCE console and click a target cluster.
- Choose Workloads in the navigation pane, and select the type of workload whose metrics are to be reported to AOM.
- Choose More > Edit YAML in the Operation column where the target workload is located.
- In the displayed dialog box, locate spec.template.spec.containers.
- Add environment parameters to the end of the image field, as shown in Figure 2.
- Click Confirm.
Parent topic: Infrastructure Monitoring
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot