-
Notifications
You must be signed in to change notification settings - Fork 140
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
🔊 [RUM-253] customize deflate worker failure logs #2414
🔊 [RUM-253] customize deflate worker failure logs #2414
Conversation
Current dependencies on/for this PR: This comment was auto-generated by Graphite. |
Current dependencies on/for this PR:
This comment was autogenerated by Freephite. |
@@ -126,6 +126,7 @@ export function makeRecorderApi( | |||
|
|||
const worker = startDeflateWorker( | |||
configuration, | |||
'Datadog Session Replay', |
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.
❓ question: any specific intent by adding "Datadog" prefix to the message?
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.
I wanted to use Datadog RUM
for the RUM Browser SDK, so to mimic this pattern I thought Datadog Session Replay
could be nice. I've seen multiple customers using different Session Replay and RUM solution at the same time, so mentioning Datadog
could help a bit.
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.
It may worth adding the Datadog
prefix for all our messages then.
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.
I'll do that in a separate PR
e6fc07b
to
4fa98c7
Compare
Motivation
In the coming PR, we'll want to start the deflate worker from different places (according to a
experimental flag/configuration option). The current error message mentioning "Session Replay" is
not adequate anymore.
Changes
This PR add the ability to adjust the error message.
Testing
I have gone over the contributing documentation.