We have a complex in house app that does something similar. Worse it can have up to 12-15 different processes running on multiple different servers in the app. Irritating
I went for a registry discovery. HKLM:\Software\MGT\AppName (all custom monitoring where we work uses the custom MGT reg key for SCOM stuff) Does this app exist on the server? If yes, then run discovery for the processes. (24hour interval is sufficient) so. ifexist: HKLM:\Software\MGT\AppName (Create app class - then use this to create the group) then run discovery for HKLM:\Software\MGT\AppName\process1 regsz 1 (if yes create class) HKLM:\Software\MGT\AppName\process2 regsz 1 (if yes create class) etc then for each if class exists, monitor Not sure if it’s the best way, but it turned out to be the most maintainable way for us. It was also my first ‘real management pack a few years ago. Then they switch me to a different team for two and a half years 😊. Now I am back and it still works fine despite several configuration changes, since the registry edits are all that’s needed when they reconfigure it. Sent from Windows Mail From: Orlebeck, Geoffrey Sent: Friday, March 6, 2015 9:51 AM To: [email protected] Looking for some guidance on “best practice” approach for monitoring processes on individual servers. I was using the Management Pack Templates > Process Monitoring to setup some monitors and applying them to a group that is based on an application. However, maybe only 1 or 2 of the servers in the group actually are supposed to have that process running. To avoid the other servers raising alerts when they shouldn’t (because the process doesn’t run there), what is the best way? Should I actually create a sub-group that contains only the relevant servers and modify the group scope of the Process Monitor? Or create a subgroup with the servers that should not be monitored and create an override to disable that alert against the group? Or is there a better way entirely that I haven’t come across in the reading I’ve done? Thank you! -Geoff Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
