-
Notifications
You must be signed in to change notification settings - Fork 619
[Dashboard] fix: Add error reason to analytics API error logs #6034
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Dashboard] fix: Add error reason to analytics API error logs #6034
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6034 +/- ##
=======================================
Coverage 54.89% 54.89%
=======================================
Files 1151 1151
Lines 61209 61209
Branches 5159 5159
=======================================
Hits 33598 33598
Misses 26883 26883
Partials 728 728
*This pull request uses carry forward flags. Click here to find out more. |
size-limit report 📦
|

title: "[SDK/Dashboard/Portal] Feature/Fix: Concise title for the changes"
If you did not copy the branch name from Linear, paste the issue tag here (format is TEAM-0000):
Notes for the reviewer
Anything important to call out? Be sure to also clarify these in your comments.
How to test
Unit tests, playground, etc.
PR-Codex overview
This PR enhances error logging in the
analytics.tsfile by including the response body in the error messages when a fetch request fails. This provides more context for debugging.Detailed summary
reasonvariable when the response status is not 200.reasonin the message for both user ops usage and client transactions stats fetch failures.