Docs: show how Logger and Metrics telemetry appears in CloudWatch Omni

Ouverte
  • Quelque chose ne va pas ?
#8,692 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@leandrodamascena y travaille déjà.

Depuis le 28/10/2026.

  • #8693 par @leandrodamascena — ouverte

Évaluation

Difficulté
2/5
Temps estimé
1-3 heures
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
aws, python
Domaine
documentation

Piste de recherche

Read the existing Logger, Metrics, and Tracer documentation sections under Observability or Advanced, then review linked issue #7003 for the OpenTelemetry context. Add the requested CloudWatch Omni subsections: a Logger example and SQL query, a Metrics EMF example, and a short Tracer note. The work is complete when all three pages explain how their telemetry appears in Omni; linked pull request #8693 is already open.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

documentation logger metrics triage
What were you searching in the docs?

How Powertools telemetry shows up in CloudWatch Omni, the new unified observability experience built on CloudWatch.

Is this related to an existing documentation section?

Logger and Metrics, with a short note in Tracer.

How can we improve?

Omni reads the telemetry that is already in CloudWatch, so everything the Logger and Metrics utilities emit is there with no extra setup: structured JSON logs land in the dataset, EMF becomes CloudWatch metrics, and fields like service, correlation_id and xray_trace_id are what the correlation and the context graph work with. Nobody can tell that from our docs today.

I'd like one small section in each page:

  • Logger: what a Powertools log line looks like once queried in an Omni space, which standard keys matter for correlation, and a sample SQL query over the dataset filtering by service and correlation_id.
  • Metrics: the EMF payload turning into a metric that an Omni alert or dashboard can use, with service as the dimension that ties it to the logs.
  • Tracer: a short note that X-Ray traces are available through Transaction Search, and that Omni is OpenTelemetry-first, pointing to #7003 for the OTel discussion.

Screenshots from a real space would help, I can provide them. No code changes.

Got a suggestion in mind?

Keep it as subsections under the existing "Observability" or "Advanced" areas of each page rather than a new page, Omni is a consumer of what we already produce.

Acknowledgment
  • I understand the final update might be different from my proposed suggestion, or refused.
Langage dominant
Python
Étoiles
3.3k
Forks
511
Merge moyen
3 j 8 h
PR mergées (30 j)
92

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de aws-powertools/powertools-lambda-python

Toutes les issues de aws-powertools/powertools-lambda-python

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.