Anomaly Detection and Cisco Cloud Observability APIs
In the Part 1 weblog [1], we talked in regards to 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 determine and react to cloud native software entity well being leveraging Health Rules APIs and Actions API.
One facet of any APM resolution is to make sure that your corporation functions are wholesome. Another key facet is to make sure that they’re performing per the metrics that you just lay out. Applications ought to be acting at or above their anticipated habits. How does one specify this anticipated habits? Can we leverage machine studying capabilities of the Full-Stack Observability resolution to study what’s regular, and flag when irregular habits of an software is detected? This is the place anomaly detection [3] is available in. This weblog will get you began with tips on how 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 sources and providers. This knowledge varieties the idea for the machine studying algorithm to determine irregular habits.
Cloud Connections with Cisco Cloud Observability
Review cloud connection API’s within the blogs referenced in [4] [5].
Fig 1. High-level overview of how Cloud Native Application Observability work
Monitoring Entity Health with Cloud Native Application Observability
For handbook 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 possibly can discover this with:
- pattern python code [8],
- sandbox [9] and
- studying lab [10].
As an 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 can evaluation the entities enabled for AD in [3].
Further studying
[1] Identify weak hyperlinks in your software stack with FSO Health Rules
[2] About Cisco Cloud Observability
[3] Anomaly Detection in Cisco Cloud Observability
[4] Leverage Abstraction To Hide 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 Exchange
[9] Sandbox
[10] Learning Lab
Share: