1 of 1 people found this helpful
You can solve this different ways. Typically, you would need to create alias formulas in the Admin console, to associate your events to the desired CI's. This is described in the Service Modelling and Publishing Guide. The out of the box alias formula are there to associate the events to the devices that the monitors are created on.
One other way to resolve this - for the CI that you want to be affected when the Apache Tomcat Service is down:
1.) Give the CI a particular alias, if you have not already done so.
2.) In the Admin console, go to the monitor that will generate the event for the Apache Tomcat service. Edit the monitor, and in the 'CI Alias' field, provide the alias of your CI.
Then, whenever that monitor generates an event, the event will be attached to that CI, rather than the BPPM device that the monitor is created under.
Hi Charles, thanks for the quick reply. I tried the second option, but when saving it I am getting the error "Cannot find Agent on PN Server with port 12124"
I am not sure which Agent it is referring to. If it is not able to connect to the Patrol agent on the target server or the the patrol agent is not able to connect to the Pnet server I would not be able to get the events from that particular target server. But I am able to receive events triggered and create incidents automatically.
That would be referring to the BPPM agent, not a PATROL agent. Are all of the processes running on the BPPM Server?
Yes all the processes are running except the service "BMC Impact Event Log Adapter for Windows".
Also the version I am using is BPPM 9.5, ITSM 8.1 on windows 2012.
I wasn't referring to the services listed in the Services Control Panel, but the BPPM processes (you can check by running 'pw system status' or 'pw p l').
Charles below are the processes running.
Please let me know if I missed any.
You should probably open a support issue to verify the bppm server & monitor configuration.
Also the license we are using is a trial license provided by BMC which is valid for another one year. Would that be the cause of the issue??