-
Notifications
You must be signed in to change notification settings - Fork 141
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
feat: add more debug signals #1743
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Your free trial has ended. If you'd like to continue receiving code reviews, you can add a payment method here: app.greptile.com/review/github.
1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile
properties['$sdk_debug_replay_internal_buffer_length'] = this.sessionRecording['buffer'].data.length | ||
properties['$sdk_debug_replay_internal_buffer_size'] = this.sessionRecording['buffer'].size | ||
} | ||
properties['$sdk_debug_retry_queue_size'] = this._retryQueue?.['queue']?.length |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this should give us a view on how much data replay is currently holding
and whether the SDK retry queue is high
hopefully giving signal that e.g. network requests to send data are failing in replay
when smaller event data might be succeeding
Size Change: +3.48 kB (+0.11%) Total Size: 3.31 MB
ℹ️ View Unchanged
|
it can be tricky to know what is happening when users report errors
let's add more debug signals
needs a follow-up to add these to core definitions