From the course: Cloud Observability and Operations: Considerations for Security, Governance, Monitoring, and Cost Control
Unlock the full course today
Join today to access over 24,900 courses taught by industry experts.
Self-healing example
From the course: Cloud Observability and Operations: Considerations for Security, Governance, Monitoring, and Cost Control
Self-healing example
- [Instructor] Self-healing in CloudOps refers to the ability of CloudOps tools, such as observability, to resolve issues without requiring human intervention. This is key to CloudOps, considering that we're attempting automatic repairs and fixes as much as we can. This increases uptime because we don't have to deal with each and every cloud system problem, but have automated tasks that can self-heal on our behalf. The best way to work through the concept of self-healing is to work through an example. Let's say that we have a public cloud-based system that has a relational database attached to an inventory application. The application is running on a Linux-based server and uses native development tools. The system has over 1,000 users working on this application at any given time, and the database is critical to the application operations. If not running, the application won't work either. Most applications are like this. This is known as tightly coupled, or there is a dependence…
Contents
-
-
-
-
Gathering ops data2m 37s
-
(Locked)
Storing ops data2m 34s
-
(Locked)
Analyzing ops data for observability2m 28s
-
(Locked)
Reacting to the data3m 5s
-
(Locked)
Automation vs. abstraction2m 50s
-
(Locked)
Self-healing example4m 6s
-
(Locked)
Cloud cost monitoring and observability (FinOps)1m 42s
-
(Locked)
Challenge: Automating operations at Jill's Scarce Wood2m 45s
-
(Locked)
Solution: Automating operations at Jill's Scarce Wood2m 34s
-
-
-
-
-
-