You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are you trying to achieve and what is your issue? Please describe.
We are trying to redirect logs/errors to the correct service/version based on the stack trace.
To do that we used the beforeSend of RUM and browser-logs.
We made it work for RUM, by simply rewriting the event.version and event.service 👍.
So we wanted to do the same for browser-logs, rewriting event.service works, but, there's no event.version.
We originally thought that the type was missing but even by forcing it, it doesn't work. The logs are indeed redirected to the right service but not to the specified version.
It seems that browser-logs beforeSend event does not support version.
Are we right? And do you plan to add it or is it an alternative available?
Describe the solution you'd like
Being able to rewrite the event.version as well for browser-logs.
Describe alternatives you've considered
No alternatives.
The text was updated successfully, but these errors were encountered:
Hello Datadog team 👋
What are you trying to achieve and what is your issue? Please describe.
We are trying to redirect logs/errors to the correct service/version based on the stack trace.
To do that we used the
beforeSend
of RUM and browser-logs.We made it work for RUM, by simply rewriting the
event.version
andevent.service
👍.So we wanted to do the same for browser-logs, rewriting
event.service
works, but, there's noevent.version
.We originally thought that the type was missing but even by forcing it, it doesn't work. The logs are indeed redirected to the right service but not to the specified version.
It seems that browser-logs
beforeSend
event does not supportversion
.Are we right? And do you plan to add it or is it an alternative available?
Describe the solution you'd like
Being able to rewrite the
event.version
as well for browser-logs.Describe alternatives you've considered
No alternatives.
The text was updated successfully, but these errors were encountered: