Skip to content

Conversation

@stefanosiano
Copy link
Contributor

DESCRIBE YOUR PR

Added Feedbacks page under Telemetry with SDK processing details.
This will help SDKs to align on the expected feedback processing.
Closes getsentry/sentry#88232

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

@vercel
Copy link

vercel bot commented Apr 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
develop-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 15, 2025 10:36am
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
changelog ⬜️ Ignored (Inspect) Visit Preview Apr 15, 2025 10:36am
sentry-docs ⬜️ Ignored (Inspect) Visit Preview Apr 15, 2025 10:36am

@stefanosiano stefanosiano changed the title Added Feedbacks page under Telemetry with SDK processing details Add Feedbacks page under Telemetry Apr 9, 2025
@stefanosiano stefanosiano requested a review from a team April 9, 2025 11:41
@aliu39 aliu39 requested a review from a team April 9, 2025 19:26
@ryan953 ryan953 requested a review from a team April 11, 2025 17:17
Copy link
Contributor

@coolguyzone coolguyzone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

stefanosiano and others added 2 commits April 14, 2025 12:02
specified SDK doesn't have to fill name and email with user context, as it's done by backend
updated scope data to apply to feedbacks
Copy link
Member

@aliu39 aliu39 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great!

@stefanosiano stefanosiano merged commit 48624ef into master Apr 15, 2025
10 checks passed
@stefanosiano stefanosiano deleted the stefanosiano/feedback-telemetry branch April 15, 2025 13:28
## Full Envelope Example

```json
{"event_id":"9ec79c33ec9942ab8353589fcb2e04dc","sent_at":"2024-03-19T15:18:27.581Z","sdk":{"name":"sentry.javascript.react","version":"7.105.0"}}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@aliu39 @billyvg I have a question to this: there should also be a DSC entry here which contains a replay_id, right? Isn't that how it's supposed to get linked with replays/traces and not via the explicit contexts.feedback.replay_id field?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bruno-garcia suggested we should include it -

it's important as I don't think we'll link the feedback to other data properly without it.

bitsandfoxes pushed a commit that referenced this pull request Apr 24, 2025
* Added Feedbacks page under Telemetry with SDK processing details
@github-actions github-actions bot locked and limited conversation to collaborators May 2, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SDK docs] add new UF data model and implementation details under telemetry dev docs

6 participants