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
-
Backend issue lists report in-patch warnings and out-of-patch errors as not publishable可能已有人在做 @RaphaelFakhri 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
mozilla/code-review#3794 ·
維護者通常 1 天內回覆
-
[oblt-aw][autodoc] Update docs that still describe the security registry as empty可能已有人在做 @github-actions 今天認領。 未關閉
難度 1/5 1-3 小時 新手友好度 85/100
維護者通常 1 天內回覆
-
[Bug] adb backup script reports "Done" & exits 0 when the backup fails可能已有人在做 @bhattmanthan 今天認領。 未關閉request-issue-assignment
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
agent-ui bug p2
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
correction metadata
難度 1/5 1 小時以內 新手友好度 72/100
acl-org/acl-anthology#10768 · 1 則留言 ·
維護者通常 1 天內回覆