I have read several of the threads, many of them much older than the current product version. I haven't explored (as I don't have direct access to the server that Solarwinds is installed on) the config file settings.
I have an Application configured with Components to monitor processes. Some processes have multiple instances, so am using the Performance Counter Monitor to monitor each individually (proc, proc#1, proce#2). My issue comes into play trying to monitor for an instance that should NOT exist. The application has a "health" process that will clean/restart processes on a scheduled basis. On occasion it will fail to kill/restart the existing process, but starts a new instance that replaces it. I have a component added to detect this, but if it doesn't exist it will have status unknown, which makes the Application appear to be down.
Because components are Events, it should not have an impact on the status of the Application. Only Alerts should have this type of impact. I have set up a monitoring rule/alert for any crititical Event for the Application to create an Alert and Email, because Alerts should be actionable, Events are simply data... used to correlated more complex criteria for an outage.
1) I suppose I could create another Application and have this process as a component of that application
2) Is there a better way to manage this over all?
Thanks for your time
