-
Notifications
You must be signed in to change notification settings - Fork 128
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
stack trace/source mapping for custom action #2703
Comments
Hello 👋 Unfortunately, only errors collected by RUM and logs of level Check more on the official documentation. |
thank you for confirming, are there any workarounds i could try using custom attributes or something similar? If not whats the recommended way of dealing with events with the same name across many different files/locations? |
yeah. basically we're using addAction all over our app to log custom actions, and I'm trying to get a consistent way of finding the exact call site in the source based on the information available on the event in the web console. The problem is that some of our events have names that are used in many different places throughout the app, so running a global search on the codebase shows multiple results. Our current solution is to just include the file name and line number in the event name, but thats too easy to mess up during refactoring or forget all together. Is there an easier/better way to uniquely identify were the actions are actually coming from? |
Hello @b3nb5n , |
Hi, if there are multiple events in the same view with the same name it could still be ambiguous where the event came from. |
Hi, Regarding this:
Could you give us an example (a code piece or implementation steps) of using |
Hey! I just got sourcemapping set up for my RUM app and its working great for errors. Is there a way to do the same thing for custom actions? i.e have an unminified stack trace visible in the datadog console for actions tracked via
datadogRum.addAction
The text was updated successfully, but these errors were encountered: