You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 second strategy I'd like to see is one that focuses on Open source augmented Strategy (AMP, AMG, etc.)
Here is the purposed section structure with labs:
Open source augmented Strategy - this approach pulls in the best of open source technologies while still taking advantage of the AWS capabilities.
Logs /events - Open source tooling logging to s3.
Metrics - introduce AMP and AMG and discuss the open source projects they pull from
[Lab] Enable gathering of Prometheus metrics into AMP and the presentation in AMG
Scraping metrics using AWS Distro for OpenTelemetry (use add-on)
Storing metrics with AMP
Accessing Grafana
Cluster Dashboards
Application Metrics
traces - open source tracing tools
Cost visibility with Kubecost - overview of Kubecost
Introduction
Cost Allocation
Kubecost and Amazon Managed Service for Prometheus
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. In this case it will also highlight how open source tools can effectively be used for EKS observability.
The text was updated successfully, but these errors were encountered:
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 second strategy I'd like to see is one that focuses on Open source augmented Strategy (AMP, AMG, etc.)
Here is the purposed section structure with labs:
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. In this case it will also highlight how open source tools can effectively be used for EKS observability.
The text was updated successfully, but these errors were encountered: