1 of 1 people found this helpful
1. No -- personally we use the HTTP post from a solar winds Alert to our service now instance to create alerts (*).
3. it works (*)
4. Others are seriously considering off-the-shelf products to provide event management as a subsequent step / CSI of our incident management process. Mostly because the non-network alerting we have (i.e. the non-Solarwinds NPM bits) are so fragmented that the [other]people responsible for that bit need some help in coming up with a solution that works.
*this is/was good as a first pass, but you will need to get some event management system if you want to put a lot of alerts into ServiceNow;
Since you mentioned eyeShare for quickly integrating Solarwinds with ServiceNow, just thought I'd mention a few things:
- The integration is bi-directional. So eyeShare can not only receive alerts from Solarwinds & automatically create tickets in ServiceNow for them, but once eyeShare resolves the underlying incident, it can go back into Solarwinds to update & dismiss the original alert. We call this a "Closed Loop Process" and eyeShare can often remediate incidents without the need for any human intervention.
- As for ServiceNow, eyeShare can not only create tickets automatically, but it can also monitor ServiceNow's request queues and launch automated workflows for them. For instance, if someone posts a request in ServiceNow to provision a VM, eyeShare can recognize & understand the request, then execute a workflow to provision the VM with whatever parameters the original request included.
- The total time required to integrate both Solarwinds AND ServiceNow is less than 5 minutes (really).