bill.goldinYou can use the *All when checking the service. First you will need to run update list by scan on the monitoring tab. Then apply the monitoring set. That will monitor all Automatic services.
Has there been any update on any of this? I am in the same boat.
Bump. Still looking for something that can do this.
Since you've resurrected this old thread, I'll throw in my $0.02...
Monitoring every service because it is set to auto start is a particularly bad idea unless you enjoy having your VSA virtually swimming in alerts. Disabling this method of alerting was one of the first things I did when coming on board about 3 years ago. This, combined with threshold adjustments of some monitors, elimination of inappropriate monitors, and using Service Desk to auto-remediate many alerts resulted in a drop in tickets by more than 62%. We now have an environment with over 3000 agents being monitored and no more than 3 engineers on help desk at any time. We also have a level of automation that insures that we don't miss alerts from missing or mis-applied monitor sets. Here's the general idea of what we deployed:
Our RMM Suite employs a daily audit process that I developed. When it detects a new role, feature, or application suite, the appropriate monitor set is applied within 5 minutes of detection. This assures that all important services and applications are monitored without manual intervention. Conversely, when a role, feature, or application is removed, the monitor is also removed within minutes of discovering that it is gone. THis minimizes the period when false alerts can occur. When we do get such an alert and the engineer determines that the application was removed, they simply run the audit process and the monitors are removed automatically. Our engineers never manually apply monitor sets of any kind except for development and testing.
The role/feature/application audit process uses a configuration file, so adding new applications is a breeze. Once the detection is built, a corresponding monitor set is developed and tested. After validating it, the manual link to the monitor is removed and a policy defined to apply it based on the detection. From that point, all future detections will apply the monitor set automatically. In all, it takes about an hour to build a new detection/monitor/policy set and verify it.
You can check out the Kaseya Automation Exchange or the mspbuilder.com web site for more information about the RMM Suite, as well as several blog articles on best practices for monitoring and other Kaseya automation processes.
Have you looked at this yet
In particular the "MSP Assist Kaseya ‘Plugin’"and the 2 video clips