getsentry / getsentry/sentry-javascript

Automatically instrument profiling for Node and Python when Sentry is set up via the Lambda Layer

未關閉
#11,800 7 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
AWS Lambda Feature: Serverless Improvement Profiles
主要語言
TypeScript
星號
8.7k
分支
1.8k
平均合併
1 天 18 小時
30 天內合併 PR
541

描述

### Problem Statement

Currently the [Lambda Layer setup instructions for serverless functions](https://docs.sentry.io/platforms/python/integrations/aws-lambda/manual-layer/#configuration-options) suggest that errors and performance is automatically enabled:

> You can configure Sentry by setting these environment variables for your Lambda function:
> `SENTRY_INITIAL_HANDLER`: The handler function of your AWS Lambda funtion.
> `SENTRY_DSN`: This is set to the [DSN](https://docs.sentry.io/product/sentry-basics/concepts/dsn-explainer/) of your project
> `SENTRY_TRACES_SAMPLE_RATE`: This sets the [sampling rate](https://docs.sentry.io/platforms/python/configuration/sampling/#sampling-transaction-events) for transactions.

(I assume this applies to both Node and Python. [The Node lambda layer docs](https://docs.sentry.io/platforms/javascript/guides/aws-lambda/layer/) are not explicit about what you get out of the box)

Beyond the above, though, it seems profiling has to be manually set up [for Node lambdas](https://docs.sentry.io/platforms/javascript/guides/aws-lambda/profiling/#enabling-profiling) and I believe also [for Python lambdas](https://docs.sentry.io/platforms/python/profiling/). This manual step can be difficult when a customer has, say 1000 lambdas and doesn't want to instrument them all with profiling individually.

### Solution Brainstorm

Add a configuration option for Node and Python profiling in the lambda layer.

### Product Area

Profiling

貢獻指南

開啟貢獻指南

研究方向

從 Lambda Layer 設定說明以及連結的 Node 和 Python profiling 文件開始。追蹤目前如何為每個 runtime 啟用 profiling,並定義 layer 設定的入口點;當一個有文件說明的設定選項能夠在不需要個別 instrumentation 的情況下,為 Node 和 Python Lambda 函式啟用 profiling 時,即表示完成。

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

評估

技術堆疊
node.js, python
領域
cloud, observability-sre
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

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

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