Skip to content
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

Sending a message with an error #48

Open
Elliot67 opened this issue Nov 10, 2023 · 0 comments
Open

Sending a message with an error #48

Elliot67 opened this issue Nov 10, 2023 · 0 comments

Comments

@Elliot67
Copy link

Elliot67 commented Nov 10, 2023

With the current implementation, text defined in the message key is sent to Sentry with the captureMessage function. Sentry then uses this message as a title in the dashboard.

If an error object is also included, the captureException function is used instead, and Sentry uses the error's message as the title of the issue. However, the text provided as the original message isn't sent, It would be great to also include it as additional data to the issue.

I believe the following changes could resolve this problem : (line 103)

- Sentry.captureException(error, { tags });
+ Sentry.captureException(error, { extra: { message }, tags });

Looking at the code, I'm also wondering if including the tags in captureException is necessary since they are already configured inside configureScope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant