A while back I wrote an introduction article on how System Center Advisor works when it is integrated with Operations Manager. Doing some more work with this recently I found a couple of additional tricks to be aware of when using Advisor in Operations Manager. This article will cover three debugging topics:
- Where does Advisor write its event information?
- Are the prerequisites for Advisor integration?
- Are there agents which may be incompatible with Advisor integration?
Where does Advisor write its event information?
The first item to be aware of is when debugging Advisor, use the Operations Manager log on the management servers in your environment. If you filter the log to the source of “Advisor” this will give quick insight into what is occurring related to Advisor (you could also collect all events from the source of Advisor if you were interested in doing so and then just view the relevant events for all management servers in an event view within Operations Manager). The screenshot below shows a subset of the filtered Operations Manager event log showing only Advisor as the Event source:
Are the prerequisites for Advisor integration?
I am currently testing the new Advisor functionality in my lab (http://preview.systemcenteradvisor.com) and ran across an event 54019 from the source of Advisor indicating that I needed to have .NET 3.5 sp1 installed as shown below. So if you are integrating Advisor and are not seeing information appear, this is a good one to check for.
Be aware that you need to have .NET 3.5 sp1 installed on your management servers if you will be integrating with Advisor.
Are there agents which may be incompatible with Advisor integration?
The health state below shows that some agents may be incompatible with Advisor. The item below is a Service Manager 2012 R2 server which is multihomed to Operations Manager 2012 R2. I have seen in multiple environments the Service Manager servers are incompatible when it comes to being integrated with Advisor.
To resolve these issues I removed these agents from being Advisor integrated after seeing these health state indications on the Service Manager servers in my environment.
Summary: Advisor integration with Operations Manager provides a lot of benefit (I’m working on a blog post related to the benefits of the alerts I’m seeing with my lab as an example). If you run into issues with Advisor integration, check the Operations Manager event logs in your environment from the source of Advisor and check the health states for the Advisor Connector Compatibility Status Monitor.