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 摘要。