Maintenance: AWS X-Ray SDK/Daemon end of life

未關閉
#7,382 1 則留言 7 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
30/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯
技術堆疊
aws, python

研究方向

Read the AWS X-Ray end-of-life documentation and the linked RFC discussion before choosing an implementation. Then locate the Powertools for AWS Lambda Python Tracer utility and determine how its supported tracing behavior and public API would need to change for an OTEL-based transition. The issue does not name files, tests, or acceptance criteria, so it is not self-contained for a first contribution.

由索引模型根據 Issue 內容生成。

描述

internal
Why is this needed?

On August 22, 2025, the AWS X-Ray team announced the end of life of the AWS X-Ray SDK and Daemon. According to its documentation, this end of life process will occur in two stages:

1/ On February 25th, 2026, the AWS X-Ray SDK will enter in the Maintenance Mode and AWS will limit X-Ray SDK and daemon releases to address only critical security issues. No new feature enhancements.

2/ From February 25th, 2027, X-Ray SDKs and daemon will no longer receive updates or releases. All published releases will continue to be available through public package managers and the code will remain on GitHub.

Regarding Powertools for AWS Python, this end of life will specifically affect customers who use our tracer utility.

As usual, we are committed to providing the best for our customers and already have a request for comments (RFC) open to discuss the OTEL implementation in Powertools for AWS. Since the planned X-Ray end of support is scheduled for February 2027, this gives us enough time to ensure we can write and deliver a smooth experience for customers transitioning to use our Tracer utility with the OTEL SDK.

I encourage you to join the discussion that will help shape our future with OTEL support: https://github.com/aws-powertools/powertools-lambda/discussions/90.

Please let us know if you have any additional questions we can help with.

Which area does this relate to?

Tracer

Solution

No response

Acknowledgment
主要語言
Python
星號
3.3k
分支
511
平均合併
3 天 8 小時
30 天內合併 PR
92

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

aws-powertools/powertools-lambda-python 的其他 Issue

查看 aws-powertools/powertools-lambda-python 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。