getsentry / getsentry/sentry-java

Align callback error handling with other SDKs

未关闭
#6,081 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
Client Reports Java Platform: Java
主要语言
Kotlin
星标
1.4k
派生
478
平均合并
2 天 22 小时
30 天内合并 PR
69

描述

### Description

Currently Java SDK does not follow the [new spec for callbacks](https://github.com/getsentry/sentry-docs/pull/19189).
If an error happens in a customer callback (hook), the SDK should fall back according to spec.

Gaps in Java SDK:
- `beforeBreadcrumb`: on error the breadcrumb is added as is, it should be dropped instead
- `eventProcessor`: on error the event/telemetry goes further in the pipeline, it should be dropped instead

Client reports:
- there's a new discard reason `callback_error ` (https://develop.sentry.dev/sdk/telemetry/client-reports/#discard-reasons-1) which should be used to make this distinguishable from things being filtered out on purpose.

贡献指南

打开贡献指南

调研方向

Start by tracing the Java SDK handling for the beforeBreadcrumb and eventProcessor callbacks, then inspect how client-report discard reasons are represented. The work is complete when callback errors drop the breadcrumb or event and record the callback_error discard reason, matching the referenced callback specification.

由索引模型根据 Issue 内容生成。

评估

技术栈
java
领域
tooling
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
66/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。