Anomaly Detection and Cisco Cloud Observability APIs
Within the Half 1 weblog [1], we talked concerning the significance of software observability and the way the appliance stack is extra complicated than ever with multi cloud deployments. We noticed how the FSO resolution, Cisco Cloud Observability [2], can be utilized to establish and react to cloud native software entity well being leveraging Well being Guidelines APIs and Actions API.
One side of any APM resolution is to make sure that your small business functions are wholesome. One other key side is to make sure that they’re performing per the metrics that you simply lay out. Functions must be acting at or above their anticipated conduct. How does one specify this anticipated conduct? Can we leverage machine studying capabilities of the Full-Stack Observability resolution to study what’s regular, and flag when irregular conduct of an software is detected? That is the place anomaly detection [3] is available in. This weblog will get you began with the right way to go about configuring anomaly detection and affiliate actions when violations are detected.
As in well being guidelines, cloud connections to your cloud accounts begins the information assortment out of your cloud assets and providers. This knowledge types the premise for the machine studying algorithm to establish irregular conduct.
Cloud Connections with Cisco Cloud Observability
Overview cloud connection API’s within the blogs referenced in [4] [5].
Fig 1. High-level overview of how Cloud Native Utility Observability work
Monitoring Entity Well being with Cloud Native Utility Observability
For guide provisioning of anomaly detection and actions with ClickOps, you’d use the Cisco Cloud Observability portal.[6]
For programmatic provisioning of well being guidelines and actions utilizing API’s [7], you’ll be able to discover this with:
- pattern python code [8],
- sandbox [9] and
- studying lab [10].
For instance, the code and sandbox use the bottom entity in you software stack, specifically compute. The identical methodology can be utilized on any supported entity within the software stack for which knowledge assortment is enabled. You’ll be able to overview the entities enabled for AD in [3].
Additional studying
[1] Determine weak hyperlinks in your software stack with FSO Well being Guidelines
[2] About Cisco Cloud Observability
[3] Anomaly Detection in Cisco Cloud Observability
[4] Leverage Abstraction To Conceal Complexity with Cisco Cloud Observability Cloud Connection API
[5] Automating Observability with Cisco Cloud Observability Cloud API’s
[6] Anomaly Detection Configuration with ClickOps
[7] API Documentation
[8] DevNet Code Alternate
[9] Sandbox
[10] Studying Lab
Share:
