Operations | Monitoring | ITSM | DevOps | Cloud

Over time, Enterprise Alert continues to grow and more and more teams are starting to benefit from Enterprise Alert’s reliable alerting. As part of this process, Enterprise Alert almost always becomes a central component of the NOC and has practically trained the NOC admins. For this reason, here in support we rarely have the pleasure of presenting the features of our alarm center.

As the famed psychologist Abraham Maslow once said, “If all you have is a hammer, everything looks like a nail.” Because IT management systems make it simple and easy to create alerts for all kinds of events and conditions, the temptation may be to create alerts for all of them. This can be problematic for a variety of reasons, though two stand out in particular.

In a network operations center (NOC), alerts originating from hundreds of servers, application monitoring systems, emails and ticketing services compete to catch a NOC analyst’s attention. NOCs face many challenges in parsing through alerts to identify actionable notifications and mobilize the right response team into action.

In this blog, we will walk through the scenario of sending or E-bonding ServiceNow incidents to 5 destinations simultaneously, using Robotic Data Automation and AIOps Studio. E-bonding refers to a scenario where data is delivered (one-way) or synchronized (two-way) between two or different systems, which are typically under different administrative boundaries. E-Bonding term originally appeared in Service Provider and Telco space (see: ATT E-Bonding).