Conversation
…, and CW Agent CRD - CloudWatch Observability add-on with OTel Container Insights (metrics only) - Grafana 12.1.7 with AMP plugin v3.0.0 - CloudWatch Agent CRD for Prometheus scraping (orders + checkout) - OTel enrichment and resource tags on telemetry - IAM role with Pod Identity for CloudWatch agent - Load generator and cleanup script
Doc update
feat(observability): Add Query with PromQL in CloudWatch content
Back Port from main
Doc update
feat(observability): Update PromQL page with validated queries and ap…
Fixing command links
Adding Images
✅ Deploy Preview for eks-workshop ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
jsgoudar
reviewed
Aug 10, 2026
jsgoudar
reviewed
Aug 10, 2026
| --- | ||
|
|
||
| In this section we'll look at gaining insight in to metrics exposed by our workloads. Some examples of these could be: | ||
| aaaaa. In this section we'll look at gaining insight in to metrics exposed by our workloads. Some examples of these could be: |
| [...] | ||
| # HELP watch_orders_total The number of orders placed | ||
| # TYPE watch_orders_total counter | ||
| watch_orders_total{productId="510a0d7e-8e83-4193-b483-e27e09ddc34d",} 2.0 |
Contributor
There was a problem hiding this comment.
will the ids be the same for every run ?
| --- | ||
|
|
||
|
|
||
| To ingest and query OpenTelemetry metrics in Amazon CloudWatch, there are two account-level settings to enable, which can be done through the AWS console, AWS CLI, or AWS SDK. The first setting enables resource tag propagation from your AWS resources to your telemetry data, the same tags that are visible in AWS Resource Explorer. The second enables OpenTelemetry metrics ingestion for CloudWatch. |
| :::info | ||
|
|
||
| The start-otel-enrichment command requires AWS CLI v2.34+. CloudShell includes the latest CLI. If running locally, update your CLI by following the [AWS CLI install guide](https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html) . | ||
| Enrichment applies only to metrics going forward and does not backfill historical telemetry data. Allow 5–10 minutes for enriched metrics to start appearing.them in CloudWatch. |
Contributor
There was a problem hiding this comment.
should the file name be opentelemetry - missing l
| Next, deploy a load generator to produce application traffic and generate order metrics: | ||
|
|
||
| ```bash test=false | ||
| $ cat <<EOF | kubectl apply -f - |
Contributor
There was a problem hiding this comment.
the same loag genrator is in opentelemetry-proml.md - can we extract it and reference from a single place , without having to udpate in 2 places
|
|
||
| **Architecture** | ||
|
|
||
| Amazon CloudWatch exposes a regional OTLP endpoint that OpenTelemetry-compatible collectors and SDKs can send metrics to directly. Metrics are stored in a high-cardinality metrics store that retains OpenTelemetry metric types including counters, histograms, gauges, and up-down counters without conversion. When enrichment is enabled, CloudWatch automatically tags vended metrics with AWS resource context such as account ID, region, cluster ARN, and resource tags from AWS Resource Explorer. This enrichment requires no manual instrumentation, enabling you to query and filter across AWS accounts, regions, and resource tags using PromQL in Amazon CloudWatch Query Studio or Amazon Managed Grafana. |
Contributor
There was a problem hiding this comment.
shouldnt we inlcude otel-architecture.webp here?
|
|
||
| **Option A: AWS Console** | ||
|
|
||
| 1. Open the Amazon CloudWatch console <ConsoleButton url="https://console.aws.amazon.com/eks/home#/clusters/eks-workshop?selectedTab=cluster-logging-tab" service="eks" label="Open EKS console"/> |
Contributor
There was a problem hiding this comment.
the instruction says open cloudwatch console, but the lable is open EKS console
jsgoudar
suggested changes
Aug 11, 2026
Contributor
Author
kathanjit
changed the title
fixing comments
svennam92
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Adding a new module to ‘Observability’ lab that ports the CloudOps “Zeus” (GitLab MR !757) OpenTelemetry Container Insights methodology. The existing container-insights (ADOT→EMF→CloudWatch) and oss-metrics (ADOT→AMP→Grafana) No labs was modified or removed.
Which issue(s) this PR fixes:
Quality checks
make test module="<module>"it was successful (see https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md)By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.