Hey all - I'm doing a trial on SAM and I can't seem to get the config right.
I want to monitor a specific service on all of my windows 10 vms.
So far I can only find instructions on how to monitor a service for one node or system.
The process is to create a template and then apply that template to all the nodes you would like monitored.
Once a template has been applied, it is now an application monitor. Since you are on a trial, the out-of-the-box alert "Alert me when an application goes down" may be enabled. If it isn't, it is short work creating a new alert just to trigger for anything named with your Application Monitor name.
Once a template has been applied, it is now an application monitor. Since you are on a trial, the out-of-the-box alert "Alert me when an application goes down" may be enabled. If it isn't, it is short work creating a new alert just to trigger for anything named with your Application Monitor name.
Got ya I was looking at the service / component alerts.
Alert me when an application goes down was disabled.
I want to alert on - Application
Scope - All objects in my environment (nothing shows up)
If I look at my application monitor templates and go to my custom one it shows assigned to 1 group (my vms). When I go to the next tab over Assigned Application Monitors nothing shows up?
Ensure you have correctly applied the Application Monitor to the Group. Assign a SAM application monitor template to groups of nodes (solarwinds.com).
In the example below, the Application Template is applied to 1 Group that contains (9) members. If the group is populated, it should show in the Assigned Application Monitors Tab as well. Change to sort by Application Monitor Template Name and see if anything shows for your template.
For the alert, you can limit the scope to the Application Name, and the trigger conditions to what you are specifically looking for.
Since you are on a trial, I don't think you can open a support ticket. A couple of things to try - Restart all the SolarWinds services - "C:\Program Files (x86)\SolarWinds\Orion\StopNetPerfMon.exe" Another option is to manually assign the template to the nodes instead of using the group. Assign templates to nodes manually to create application monitors (solarwinds.com)
Trail modules do funny things at times. I faced similar kind of scenario where basic feature of SRM was not working. I restarted the solarwinds servers and post next DB maintenance It started working as expected.
Worth giving it a try if you haven't already.
Trail modules do funny things at times. I faced similar kind of scenario where basic feature of SRM was not working. I restarted the solarwinds servers and post next DB maintenance It started working as expected.
Worth giving it a try if you haven't already.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.