Proposal: CloudWatch trace export sample (python/03-integrate/observability/cloudwatch/)

Aperta
#313 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
28/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
aws, python
Ambito
observability

Direzione di ricerca

This is a proposal waiting on maintainer approval of placement and scope, so confirm the direction in the thread before writing code. The reference is the existing python/03-integrate/observability/arize sample, which should show the expected layout for requirements.txt, .env.example and the README. Done means runnable Python scripts for both direct OTLP with SigV4 signing and the ADOT collector path, with the collector config checked in, verified end-to-end in CloudWatch Transaction Search.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

harness-sdk docs PR strands-agents/harness-sdk#2980 (for strands-agents/harness-sdk#2567) added a CloudWatch trace-export walkthrough, and review there asked to move it into the examples section. The Sep 21 site redesign (strands-agents/harness-sdk#4446) retired the in-docs examples in favour of this repo's catalog, so I'd like to land it here instead, as an integration sample next to python/03-integrate/observability/arize.

Proposed scope (python/03-integrate/observability/cloudwatch/): a runnable Strands agent that exports traces to CloudWatch two ways:

  1. Direct OTLP: send traces straight to the CloudWatch OTLP endpoint with SigV4 signing, no collector.
  2. Via an ADOT collector: with a collector config checked in.

It would be Python scripts (not notebooks) with requirements.txt, .env.example and a README following the use-case template, verified end-to-end against CloudWatch Transaction Search.

Relation to #271: that PR's 04_backend_export notebook shows the ADOT path briefly as part of a learn-track tutorial, and per your July feedback it's being reworked toward use-case patterns. This sample would be the backend-integration reference that tutorials can link to, with the direct-OTLP/SigV4 path being the part not covered elsewhere.

Does this placement and scope work for you before I open a PR?

Lingua principale
Python
Stelle
897
Fork
450
Merge medio
1g 9h
PR unite (30g)
9

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di strands-agents/samples

Tutte le issue di strands-agents/samples

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.