ThousandEyes ServiceNow Integration
Evanios now offers an out-of-the-box ThousandEyes ServiceNow Push integration for customers who want the fastest and most comprehensive way of connecting this popular management software to the leading ITSM platform.
ThousandEyes is a software-as-a-service product that uses synthetic monitoring probes to measure performance. The product includes elements of network tomography for loss and latency, route analytics to visualize BGP advertisements, DNS monitoring, VoIP monitoring, and website monitoring for HTTP and HTTPS.
About Evanios’ ThousandEyes ServiceNow integration
Evanios’ ThousandEyes integration leverages the ThousandEyes Monitor Services via webhooks. We configure ThousandEyes to push alerts into our ServiceNow App and like other pre-packaged ServiceNow integrations from Evanios, set up is usually complete within a few hours with minimal training and/or customization required (Evanios is built natively on the ServiceNow platform, so there’s a very short learning curve). Simply setup our evanios integration agent with a ThousandEyes instance and user for monitoring and Evanios will parse, normalize, and process the event data.
Why Use Evanios to Integrate ThousandEyes to ServiceNow?
Evanios is an event and operations management solution that runs directly on ServiceNow. It collects events from your monitoring solutions and acts as a manager for them. With Evanios, you get an overall view of your IT environment including which events can be de-duplicated, correlated, and acted upon – often through automation.
Creating an Event Management layer between the monitoring systems and ServiceNow’s incident application provides a more effective way to create tickets in the service desk. Enriching events with all available data creates more meaningful incidents. But the reasons for using Evanios don’t stop there. Evanios Operations processes are defined in ITIL v3 Service Operation, and because the Evanios Event Management solution is a native ServiceNow application, it is able to leverage ITSM data from other applications. This is particularly helpful in circumstances where the response to an event can be changed based on its definition, the CMDB, or the business services it may impact. For example, the response might be handled differently if you are in the middle of an active scheduled change (Let’s face it: No one wants to get a wake up call for a scheduled change!).