In the Part 1 blog , we talked about the importance of application observability and how the application stack is more complex than ever with multi cloud deployments.
We saw how the FSO solution, Cisco Cloud Observability , can be used to identify and react to cloud native application entity health leveraging Health Rules APIs and Actions API. One aspect of any APM solution is to ensure that your business applications are healthy.
Another key aspect is to ensure that they are performing per the metrics that you lay out.
Applications should be performing at or above their expected behavior.
This blog gets you started with how to go about configuring anomaly detection and associate actions when violations are detected.
As in health rules, cloud connections to your cloud accounts starts the data collection from your cloud resources and services.
This data forms the basis for the machine learning algorithm to identify abnormal behavior.
Review cloud connection API's in the blogs referenced in.
High-level overview of how Cloud Native Application Observability work.
For manual provisioning of anomaly detection and actions with ClickOps, you would use the Cisco Cloud Observability portal.
The code and sandbox use the lowest entity in you application stack, namely compute.
The same methodology can be used on any supported entity in the application stack for which data collection is enabled.
This Cyber News was published on feedpress.me. Publication date: Thu, 22 Feb 2024 21:43:08 +0000