Atera excessively noisy
Does anyone else think that Atera can be excessively noisy when it comes to alerts? The main source of the noise is when disk or CPU reaches thresholds and then fluctuates either side of the threshold. That can generate 10's of alerts per day for that device. The issue became much worse when thresholds went to 2 decimal places.
I raised an "idea" many years ago with a suggestion to have thresholds on thresholds so for example, if disk usage has gone above threshold then it must go a certain percentage below threshold before the alert is cleared e.g. if threshold is 90% then it must go below 85% before it's cleared. That way we get an alert just once until the issue is properly resolved.
There should also be a limit on alerts per day. For example, someone may be doing something that generates a CPU alert. We only need to know about this once, not every time it happens.
Does anyone else agree?
Topics
- All Topics
- 41 Getting started
- 25 Read before posting
- 8 Meet and greet
- 245 General
- 67 News and announcements
- 2 Swag
- 1 Roadmap updates
- 80 Resources
- 12 Knowledge Base
- 17 Webinars
- 1 Shared Script Library
- 2 Blog
- 19 Pro Tips
- 27 Got an idea?
- 3 Atera Academy
- 2 ActionAI
- 1 Copilot
- 140 Remote Monitoring and Management
- 84 Remote Monitoring
- 27 Patch Management
- 106 Professional Services Automation
- 65 Helpdesk
- 17 Billing
- 21 Reporting
- 39 Integrations & add-ons
- 21 Integrations
- 11 Add-ons
- 105 Scripting and automations
- 62 Scripts
- 30 Automations