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.
Monitoring some things
From the course: Cloud Observability and Operations: Considerations for Security, Governance, Monitoring, and Cost Control
Monitoring some things
- [Instructor] Monitoring some but not all things is a more realistic approach. But again, it depends on what your business case is for operations and the types of cloud systems that you're operating. The theme here is to only collect operational data that is meaningful to the true observability of those systems in terms of what's going on, what went on, and what does it mean. So, while it would be easy to turn on all IO data from all cloud storage systems by the second to watch observability trends that may indicate a problem, that data at that level of granularity is overkill. Indeed, it may be easier to gather aggregated data or data that is summarized for a specific period of time. This could be something like looking at the average IO performance data per hour that's calculated on the fly before being sent to the observability database. You can pretty much determine what you need to understand by the data, and you're…
Contents
-
-
-
-
-
Monitoring everything1m 43s
-
(Locked)
Monitoring some things1m 52s
-
(Locked)
Minimum viable cloud monitoring and observability2m 13s
-
(Locked)
Leveraging people for CloudOps and observability2m 31s
-
(Locked)
Leveraging automation for CloudOps and observability2m 41s
-
(Locked)
Generative AI observability2m 42s
-
(Locked)
Agentic AI observability3m 6s
-
(Locked)
Challenge: Leveraging the Cloud Ops team effectively at Jill's Scarce Wood1m 25s
-
(Locked)
Solution: Leveraging the Cloud Ops team effectively at Jill's Scarce Wood1m 57s
-
-
-
-
-