Azure Monitor
An Azure service that is used to collect, analyze, and act on telemetry data from Azure and on-premises environments.
Cohesity Azure cluster space Issue in Azure Clusters caused by Monitor Agent
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(188.79999999999998, 67%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEJ%3C/text%3E%3C/svg%3E)
Eric J. Burnett
0
Reputation points
How do I disable the azure monitor agent or reduce its logging limit, as per Microsoft recommendations?
Symptom
Alert reports DiskSpaceLow, on Cohesity in Azure clusters:
ALERT CODE : CE00101007 ALERT TYPE : 1007 ALERT CATEGORY : Disk ALERT SEVERITY : Info ALERT STATE : Open LAST RAISED TIME : Thursday, 14-Apr-22 09:00:00 EDT ALERT NAME : DiskSpaceLow ALERT DESCRIPTION : Disk free space is low on the node 904324852649638 with ip xxx.xxx.xxx.xxx. ALERT CAUSE : Free disk space 3% on / is below the threshold 5%
Cause
This is a known scenario caused by Azure Monitoring Agent overlogging.
Resolution
To confirm this is the exact scenario you're experiencing, follow the steps below: Step 1 of 3. The /var dir should be below 200 MB, use the command below to check:
$ sudo du -xh -d1 / | sort This example shows a problematic /var size.
Step 2 of 3. Check the amount of space being used by /azuremonitoragent:
$ sudo du -xhd1 /var/opt/microsoft/azuremonitoragent | sort This example shows most space being used by Azure Monitor Agent (events).
Step 3 of 3. Disable the azure monitor agent or reduce its logging limit, as per Microsoft recommendations.
- More details can be found at How to troubleshoot issues with the Log Analytics agent for Linux.
- For assistance with Azure's Monitoring Tool, please contact Microsoft Support and provide the above information.
See Also
- Article Number 000003089: Alert: CE00101007 DiskSpaceLow.
- Cohesity recommends enabling Support Channel for remote access by a qualified support engineer.
Azure Monitor
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(70.4, 6%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
Siva shunmugam Nadessin 160 Reputation points Microsoft External Staff Moderator2025-08-11T23:22:50.09+00:00 Hello Eric J. Burnett,
To resolve the logging issue, you might either want to reduce its logging limit or disable it altogether. Here are your options:
- Reduce Logging Limit: Unfortunately, the exact configuration to change the logging limit wasn’t provided, but you can typically do this in the agent’s configuration files, adjusting any "log level" settings.
- Disable the Agent: If you're looking to disable the Azure Monitor Agent temporarily to analyze the situation, you can do so with:
- sudo systemctl stop azuremonitoragent
- sudo systemctl disable azuremonitoragent
- Review Documentation: For detailed troubleshooting, you can refer to these two articles:
If the comment was helpful, please click "Upvote".
Thanks,
Siva shunmugam.
Sign in to comment
Sign in to answer