Use Mist SLEs and Insights with APIs

When you use the Juniper Mist portal to monitor the operation of your network, you gain insight into what’s happening before it becomes an issue. You can see the network from multiple viewpoints: wireless, wired, WAN, and others. Additionally, you can use the tools that Juniper Mist™ provides to troubleshoot and correct potential issues.

The primary Mist dashboard at Monitor > Service Levels presents the results of the Predictive Analytics and Correlation Engine (PACE), in the form of Service Level Expectation (SLE) metrics. SLEs leverage machine learning and the Mist PACE in the Juniper Mist cloud. Using these resources, SLEs turn streaming telemetry from the access points (APs) into visualizations representing end users' network experience in near real time. For more information about SLEs, see the Juniper Mist AI-Native Operations Guide.

As with everything seen in the Mist GUI, SLEs and Insights information are also available from the API.

SLEs

It may be useful for you to gather information on specific SLEs to use for historical reporting purposes or to trigger other automation. Like other API calls, you begin by determining which endpoint you want to gather data from. The following is an example of the API GET request for the getOrgsSitesSle endpoint:

For more information, see SLEs Overview.

Insights

Insights provide an overview of network experience across the entire Site, Access Points, or wireless Client. It’s a great place to start when checking on a site.

You can find Insight information by making a GET request to one of the following Insights endpoints:

GetSiteInsightMetrics
GetSiteInsightMetricsForDevice
GetSiteInsightMetricsForClient

For more information, see Insights Overview.

Metrics and Classifiers

Juniper Mist SLEs and Insights endpoints support metrics and classifiers. Metrics track whether the service level meets the configured threshold value. If a metric does not meet the threshold, then this failure may be attributed to one of the classifiers to further understand where the failure occurred.

The SLE and Insights endpoints often require the metric argument. This is because, in addition to raw statistics or configuration, Mist exposes calculated values resulting from internal data analysis. Rather than creating a unique API function every time a new data analytics feature is added, Mist exposes just a handful of function, but uses the metric argument to specify which derived data values to retrieve.

To get a list of insight metrics, you can issue the following GET call:

The response would look like this:

Another way to view examples of available Insight metrics is by logging into the Mist portal and opening this link in a new tab from the same browser:

https://api.mist.com/api/v1/const/insight_metrics

Using the previous GET call example GET /api/v1/const/insight_metrics, you would add your desired metric at the end of the call. See the example GET calls below for some of the currently supported metrics and their classifiers.

AP Uptime: ap-availability

GET call:Sample Request:Sample Response:

AP Reboot: ap-reboot
AP Unreachable: ap-unreachable
Site Down: site-down

Capacity: capacity