Troubleshooting tips for your SCSM SCOM Alert Connector

re: Troubleshooting tips for your SCSM SCOM Alert Connector

Robert — Thu, 19 Apr 2012 19:58:15 GMT

We are using the SCOM connector to create incidents within Service Manager and I always see that the incidents that it creates, it places the Operations Manager Server in the Affected Items field. When reports are run against the affected item we see all events for the SCOM server rather than the 'Source' that the original alert was generated for in SCOM.

Is it possible to push the 'Source' object from the SCOM alert into the 'Affected Items' field on a template in Service Manager when the connector is used to automatically create Incidents?

re: Troubleshooting tips for your SCSM SCOM Alert Connector

Fernando — Tue, 29 Jun 2010 11:16:32 GMT

Multiple SCSM - SCOM connectors

We have used multiple connectors to be able to filter P1 and P3 calls. E.g. One connector only allows Availability Critical alerts to be sent through. These match up to P1 Templates in SCSM.

While all the rest of the critical alerts are sent through a differnet connector that match up to P3 templates.

Thats how we are doing it now.. Does anyone have any comments on this ? Any other better way to do it besides overrides to set the severity and priority of each monitor ?

Fernando