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

Abierto
#313 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
28/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, python

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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?

Lenguaje dominante
Python
Estrellas
897
Forks
450
Merge medio
1 d 9 h
PR fusionados (30 d)
9

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de strands-agents/samples

Todos los issues de strands-agents/samples

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.