Hi, We are using the OpsMgr Connector for HP OMW. We are finding it somewhat chatty. Is there a basic way to monitor this connector at a high level (e.g. healthstate monitoring to verify OpsMgr to OMW and OMW to OpsMgr are working)? Thanks, MeoJ

Is this the wrong place for this question? Is anyone using this connector and have any experiences they can share in monitoring main health status? Thanks, MeoJ

If you want to make the connector less chatty you can control what is passed trought the connector at connector level in subscriptions when you edit the properties of the connector. As for the monitoring of the connector itself I have not seen any solutions for this. - Vince

Hi Vince, Thanks for the response. We are ok with what is actually passing through the connector when both ends are working. We do have issues with the connector staying stable on both sides. For example, here are some recent messages we saw: "The connector service caught an exception while attempting to update alerts with the Operations Manager SDK Service. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "An SQL Exception has occurred while removing cache data from the SCInteropt database. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service threw an exception because no providers could be contacted to send alerts. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service threw an exception because no providers could be contacted to get update events. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service threw a WSMan unauthorized access exception when attempting to send alerts to provider. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service threw a WSMan COM exception when attempting to send alerts to provider. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service is being stopped by the Service Control Manager. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service could not locate the alert in the GetAlertsById Method. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "The Connector service received an error getting cache id. Management Pack: Microsoft.SystemCenter.Interop.Connector.Common.Library" "Description=The database cache will not be loaded because an SQL Exception occurred while starting the connector service... "Description=An SQL Exception has occurred while retrieving cache data from the SCInterop database...." Some of these are different events, others are all in the same time frame. My goal here is to be able to verify the connector is working in each direction, while keeping the noise to a minimum. Any insight is appreciated. Thanks, MeoJ

I can imagine creating some sort of synthetic transaction that is triggered in OpsMgr then sent to OMW over the connector. If you can automate an action in OMW to return a responce over the connector you could monitor this process in OpsMgr. An other strategy would be to monitor the error events generated (as you described in your post) in the eventlog. Hope this helps, Vince

Hi MeoJ, I'm having the same issues right now, were you able to fix the problem??

No activity for a long time, will mark as answer. Feel free to re-open. ThanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se