Docs: show how Logger and Metrics telemetry appears in CloudWatch Omni
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- aws, python
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
serviceandcorrelation_id. - Metrics: the EMF payload turning into a metric that an Omni alert or dashboard can use, with
serviceas 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.
- 主要语言
- Python
- 星标
- 3.3k
- 派生
- 511
- 平均合并
- 3 天 4 小时
- 30 天内合并 PR
- 98
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
aws-powertools/powertools-lambda-python 的其他 Issue
-
Bug: POWERTOOLS_IDEMPOTENCY_DISABLED set to an empty or non-boolean value crashes every invocation可能已有人在做 @lechakrawarthy 于 2 天前认领。 未关闭bug good first issue help wanted idempotency
难度 2/5 1-3 小时 新手友好度 85/100
aws-powertools/powertools-lambda-python#8728 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Bug: Redis layer fails the invocation instead of retrying when a record expires between SET NX and GET可能已有人在做 @coughlmao 于 2 天前认领。 未关闭bug good first issue help wanted idempotency
难度 2/5 1-3 小时 新手友好度 85/100
aws-powertools/powertools-lambda-python#8727 · 4 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Bug: Redis orphan lock timeout ignores expires_after_seconds and is always 10 seconds可能已有人在做 @CJstate 于 2 天前认领。 未关闭bug good first issue help wanted idempotency
难度 2/5 1-3 小时 新手友好度 75/100
aws-powertools/powertools-lambda-python#8726 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Bug: idempotency payloads with set, frozenset or bytes fields cannot be hashed可能已有人在做 @Neeraj111010 于 2 天前认领。 未关闭bug good first issue help wanted idempotency
难度 2/5 1-3 小时 新手友好度 80/100
aws-powertools/powertools-lambda-python#8725 · 6 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Bug: with a DynamoDB composite key, DataRecord.idempotency_key is the static partition key value可能已有人在做 @sumedh-aerram 于 2 天前认领。 未关闭bug good first issue help wanted idempotency
难度 2/5 1-3 小时 新手友好度 90/100
aws-powertools/powertools-lambda-python#8724 · 3 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 aws-powertools/powertools-lambda-python 的全部 Issue
相似的 Issue
-
Paraxial.trace returns NaN for an object at infinity when the entrance pupil is at the first surface未关闭
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
enhancement ios launcher
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Substrait consumer doesn't recognise `shift_left` / `shift_right` from functions_arithmetic.yaml未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
apache/datafusion#27059 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 85/100
loteran/Arctis-Sound-Manager#368 ·
维护者通常 1 天内回复
-
feed submission
难度 2/5 1-3 小时 新手友好度 65/100
MobilityData/mobility-database-catalogs#1787 ·
维护者通常 2 天内回复