This is the third of a three part blog series highlighting the integration available between System Center Operations Manager 2012 and SolarWinds Server & Application Monitor. This topic was initially mentioned around the timeframe of the Microsoft Management Summit this year – information is available at: http://myitforum.com/myitforumwp/2013/04/09/monitor-the-monitor-alert-on-operations-manager-health/.
I’ve been working with the folks at SolarWinds to provide a win/win between these two products – focusing on the “Monitor the Monitor” question. In many client engagements, the question is raised – “Who is monitoring the monitor solution?” For environments which have both of these products, each product can answer this for the other product. In the first part of the series, we discussed what steps are involved and what to expect when integrating the SolarWinds management pack for Operations Manager 2012. In the second blog post we will discussed the “Monitor the Monitor” solutions available from SolarWinds for monitoring Operations Manager. In this blog post we will reverse the second blog post and see how Operations Manager can monitor SolarWinds for the “Monitor the Monitor” question.
What monitoring for SolarWinds server health are available in Operations Manager?
SolarWinds provides a management pack for Operations Manager which provides health information for the SolarWinds Server Database and Server Web Console within Operating Manager. This management pack has a view available in the Monitoring pane (shown below) which provides these health states:
Configuring the SolarWinds health monitoring for Operations Manager:
While the SolarWinds server database is monitored, it does need to generate an alert when an error occurs.
To change this behavior, create an override which enables the Alerting flag for the SolarWinds Server Database as shown below.
Additionally, there appears to be a bug with how the SolarWinds Web Console monitoring works (it goes red on the first outage and will not reset health back to green).
Once overridden, this will disable the SolarWinds Server Web Console monitoring as shown below.
So create an override to disable this monitor next.
Finally, we need a replacement functionality to monitor the SolarWinds website. To do this, create a new Web Transaction Availability monitor (in the Authoring pane, Management Pack Templates) to monitor the SolarWinds web console.
You will also need to create a run as account which has rights to log into the SolarWinds website and configure the web transaction to use the account.
Once this monitor is functional, it will appear as shown below.
And viola! Operations Manager is now monitoring the critical pieces of my SolarWinds environment – effectively answering the “Whose monitoring the monitor” question using Operations Manager to provide the “Monitor the Monitor” solution for SolarWinds.
Summary: With the SolarWinds management pack and a few quick customizations it’s easy to provide the Monitor the Monitor solution for SolarWinds with Operations Manager. As a bonus blog post on this topic, I will be showing how to use network devices from different sources together in a single distributed application (next week!).