The new script-based threshold item is a really great addition, but it highlights an important component missing from Atera - inheritance.

When applying thresholds to endpoints, it's necessary to have thresholds inherit monitors from upstream thresholds. Right now in Atera, only one threshold can be applied to any endpoint at a time. What we need are thresholds that can build upon each other and overwrite values based on where the value changes.

For instance, I'd like to configure a top level (default) threshold to apply to everyone, but then get more specific with thresholds at a customer, and even more specific with thresholds on folders. Application of thresholds is pretty straightforward and goes like this: apply the closest threshold to an endpoint, then apply the next closest threshold and discard any monitors that are already applied to the endpoint, then keep moving up the chain until you reach the top level threshold.

This way, we can get really creative and automate much more than we currently can.

Here's an example. Most of us have an anti-malware solution which has an installer per customer. If inheritance was implemented we could set a threshold profile for the customer that only contains a single script-based monitor to check for the presense of the anti-malware solution, if it isn't found then attach an auto-healing script to the monitor to get it installed. This would then leave the rest of the monitors at a higher level threshold profile undisturbed so they can continue to work on the endpoint as required. Now we don't have to clone threshold profiles to monitor the things we need - that becomes a nightmare to manage when you need to update them.