I have previously been using Configuration Templates to exclude disk partitions from monitoring for a few months and that was working fine. With the recent conversion to Configuration Rules though, it seems I'm not longer able to exclude disk partitions. I have tried both regex pattern like /snap.* as well as string match of /snap* but a series of /snap/... partitions remain in the list and result in false alerts as these EC2 partitions always report as 100% full.
Any suggestions or help appreciated.
Dear user,
We apologize for the problem you are facing. I assume that you are using both EC2 and Server agent for your monitoring. We have identified an issue for EC2 with server monitoring and are working on fixing it with high priority. Will update here once it goes live.
-Jasper
Product Manager, Site24x7
Hey There,
The issue is fixed and its live now. Please let us know if works.
-Jasper
Hi Jasper,
Thanks to you and the team for pushing out a fix so quickly. Unfortunately though the issue I'm having remains. At present I am using just the server agent. I had previously been using the AWS agent/monitor as well but stopped that for similar reason... I couldn't exclude disk partitions. That was before the switch to configuration rules though. I'm happy to provide any details that would be helpful in finding this issue.
Thanks,
Brian
Hey Brian,
Thanks for coming back. We need to look at your account logs for us to troubleshoot further. Can you please contact support@site24x7.com. I'll summarize here once we fix the issue for you.
-Jasper
We are having this issue as well. Any instance that has the AWS ssm agent alerts for the /snap* partitions. We are using both EC2 and server monitoring. Should these partitions automatically be ignored or do we need to create some kind of exclusion list?
Running linux agent version 17.5.6.