Hello Abrar Adil S,
Thanks for posting your question in the Microsoft Q&A forum.
Here’s some information that might help you understand the situation better.
Understanding the Issue
The Azure Monitor Agent collects various performance metrics and logs from your VM, and sometimes it may create system groups or users depending on its configuration and operational needs. However, the creation of a group like azuremetricsext should ideally be documented.
Suggested Actions
Check the AMA Configuration: Review your Data Collection Rules (DCRs) and any custom configurations you may have set up. Ensure that nothing in your DCR or performance counters is triggering this behavior.
Monitoring Logs: Investigate the logs for the Azure Monitor Agent on your Linux VM. Logs may provide insights into why this group was created:
Cat->var->opt->Microsoft->azuremonitoragent->logs->azuremonitoragent.log
Review System Changes: Look into the history of any recent changes made on the VM or the Azure environment, such as the updates or modifications to the data collection settings.
Reference Documentation
While I wasn't able to find specific documentation on the creation of this particular group, here are a few resources that might help you understand and troubleshoot the AMA better:
- Learn How to Collect Performance Counters and Custom Logs Using the Azure Monitor Agent (AMA)
- Azure Monitor Agent Overview
- Troubleshooting guidance for the Azure Monitor agent on Linux virtual machines and scale sets
Let me know if you have further questions?