Observability Module: Strategies: AWS Native Strategy

[StevenDavid]

What would you like to be added?

It will be helpful to the participants to organize the majority of the Observability module into over arching strategies for creating an observability solution for their organization. The first strategy I'd like to see is one that focuses on AWS Native services (CloudWatch, X-ray, etc.)

Here is the purposed section structure with labs:

• AWS Native Strategy - this approach leverages AWS native tools as the primary approach to creating a comprehensive observability solution.
  • Logs - basics of CloudWatch logging, understand the logs, show log insights
    • [Lab] Log pattern search
    • [Lab] Log anomaly detection
  • Metrics - overview of CloudWatch metrics and Container Insights
    • [Lab] Kinds of Metrics that already exist for EKS and how we can gather custom metrics
    • [Lab] Container Insights show the value and insights into an application workload
    • [Lab] Dashboards and pre-build dashboards.
  • Tracing - overview of tracing with x-ray
    • [Lab] that walks through following traces across a given workload.
  • Profiling - overview of Applications Signals
    • [Lab] Leverage Synthetics Canaries to create health checks and demonstrate a foundational traffic flow in the cluster
    • [Lab] bring it all together with a use case flow that uses App Signals to rapidly get to the issue.
    • [Lab] Show how SLOs can be used to track down overall service performance issues.
  • Strategy summary page - summarize how this strategy helps the customer manage there workloads and infrastructure

Why is this needed?

This will help lab participates walk away with a sense of not just how to deploy individual observability components but how to use them to create a workable observability solution.