Solarwinds Integration with ServiceNow Event Management

[tarushgupta]

Hi, I am trying to integrate Solarwinds with ServiceNow event management. I am on Fuji version.

As per Wiki, ServiceNow can only connect with Solarwinds Log and Event Manager for this integration. When I setup the Solarwinds connector, I give the hostname of the Solarwinds LEM (Log and Event Manager). However, after going through mid server logs, I can see that ServiceNow tries to locate https://<ip>:17778/SolarWinds/InformationService?wsdl

But as per Solarwinds, this WSDl does not hosts on LEM server. Instead it can be found on Solarwinds SAM (Server and Application Manager) server. I have verified that the WSDL exists on SAM but not on LEM.

Still ServiceNow expects this WSDL on LEM.

has anyone done this integration in last 1-2 months since Fuji has introduced Event Management integration with Solarwinds ?

Any assistance would be appreciated.

[Tony Branton]

The wiki article is incorrect and needs to be updated - the connector is actually intended for SolarWinds SAM, not Log & Event Manager.

[Steven Young]

i cant speak for everyone,   However:

Our organization decided on using the Integration by Evanios.  

When we decided on using this, the contact was made, a Webex was setup for something like 2 days later (scheduling on both sides prevented a quicker turnaround).   These people were so good they did it the day before thanksgiving.   Yes,   Thanksgiving, when everyone else was home with their family, they helped us get set up.

A 1 hour webex and we were receiving events from solarwinds.

This integration is very well built with all back end scripting done for you.   All you need to do is tell the fields what to do.   You dont have to do any elaborate scripting.   In fact the only real scripting that you need to do is if you want this to do something that is already not built in.

During implementation i had 1 issue that i couldn't figure out.   i emailed Evanios and had a webex the following day.   They really are good about supporting their integration.

In fact, let me tell you where we are at now.   Currently our integration is set up to send events to both Dev and Prod environments.   This was kind of a rushed thing because they wanted the monitoring turned on...   Then we turned it on, and the organization said that was toooo fast, and we turned it off.   We now have a Go-Live date of January 4, 2016   at 8am.

Some other integrations take weeks to build, setup, test.   This one you can basically use the out of the box settings and just edit a few fields and it will start generating tickets.   I could not believe how   easy this was.

Of everything out there, i cant speak for anything other than the Evanios Operations.   But i would definitely recommend it.