Using AppNeta's API for Better Monitoring Data Integration
by Christine Cignoli on

APIs are the currency of today’s SaaS-based infrastructures. They allow business IT teams to connect applications in useful, creative ways to meet their particular needs. As a SaaS-based company ourselves, and with most of our customers moving their apps to cloud and SaaS models, our API powers a lot of very cool interconnected infrastructures. All of AppNeta’s detailed metrics and data points are available through our API, with the goal of offering users as much flexibility as possible.

APIs, in general, are appealing for their flexibility and the possibilities they enable. The AppNeta REST web service API, presented in a standard JSON format, for example, can be used for as basic a task as exporting monitoring data to Excel if raw data is what’s needed. AppNeta endpoint data is presented in the Swagger user interface, so you can create the curl syntax for the query.

Customers take advantage of the API to connect various types of monitoring and applications. They may pull AppNeta’s advanced monitoring metrics into the dashboard of another tool, like a more basic monitoring tool, to see all their network and application data to correlate events and alerts. For large enterprises running a busy network operations center (NOC), they use the AppNeta API as part of viewing all platforms on one screen.

As end-user experience monitoring becomes more important, pulling data into one common, central location is essential for many customers. When there is an alert on a potential issue and a customer needs to troubleshoot, they then explore the AppNeta user interface to find isolate the root cause, for a faster Mean Time to Resolution. Since we monitor continuously, our users can understand the event,where and when it occurred, to ensure the end users are back up to speed faster.

We’ve also seen, in this trend toward API-connected, SaaS-driven environments, that a lot of IT team members want to go beyond email alerts and become more proactive about network issues. With legacy monitoring, the primary method of alerting was SNMP traps that trigger an email if there’s a deviation. Those also usually involve some false positives. This method still helps IT teams, but many businesses are looking ahead to better ways to get alerts. Customers use AppNeta’s API to export our alerts into other systems. We also help with integrations into systems like ServiceNow through scripting and coding.

Business intelligence tools like Domo also lend themselves to using a monitoring API. Using AppNeta to integrate into ServiceNow and Domo can also be useful for busy customer IT teams. This kind of operational integration means they get our continuous monitoring data constantly, without having to log in to get the information they need.

How Our Customers Use the AppNeta API

We’ve seen some great uses of the AppNeta API in our customer environments. Some of our customers are API experts, and they get up and running quickly. Others call on our customer support team to figure out the best way to operationalize the API (luckily, we’ve got API experts on hand here). Here are a few of our favorite API uses:

  1. To build a customer dashboard. One of the most impressive and complex uses of the AppNeta API is a dashboard a customer created, built entirely in-house. They wrote an entire dashboard from the monitoring data they gathered through AppNeta for multiple applications.  They’ve got about a dozen services pulled in to the dashboard, which they offer to their users. That dashboard contains the history of when services were up or down.
  2. In the NOC. We see customers use the AppNeta API for real-time alerts in their network operations centers. They pull the monitoring data that AppNeta gathers into existing monitoring and ticketing systems. That includes importing events into existing processes, and doing comparisons of various monitoring data. It’s easy to set up, and takes only a quick configuration in the API: When an event occurs, it’s reported to a site. Every time there’s a violation, the API sends a message to the defined endpoint, whether it’s a URL or location. Customers have the flexibility of getting data into their systems however they’d like.
  3. For on-demand path creation. The AppNeta API can create new monitoring paths on-demand, collect results, then get rid of that path. This is especially useful with SaaS applications or dynamic cloud instances or to test the path to a particular location.
  4. To perform bulk operations. For customers who are managing hundreds or thousands of network paths or Monitoring Points, the API can be particularly useful for renaming paths. We’ve seen our users perform bulk operations across network paths when the company changes its name or relaunches a product. If past naming conventions don’t match up, they can change path names all at once instead of doing it one at a time in the web interface.

There are plenty more details here about our API presentation, so you can use your AppNeta monitoring data in the way that’s best for your business.

Filed Under: Company News, Performance Monitoring

Tags: API , AppNeta Performance Manager , end user experience monitoring , performance metrics