How to pass extra data via captureException/captureMessage in latest sdk

[smilexu]

• Review the documentation: https://docs.sentry.io/
• Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• Use the latest release: https://github.com/getsentry/sentry-javascript/releases

Package + Version

• @sentry/browser
• @sentry/node
• raven-js
• raven-node (raven for node)
• other:

Version:

4.0.6

Description

We can put a extra data in captureException / captureMessage when we use raven-js.
Raven.captureException(err, extra)

How is that supported in latest sdk ?

[Nabellaleen]

Same problem here, and it's quite a bad news, because we're loosing all the information about current errors

And we can't go back to previous Raven version due to CDN issues ...

[ValkyrieUK]

Chaps, I've been running into the same issues. Check out this.
https://github.com/getsentry/sentry-javascript/tree/master/packages/node

Sentry.configureScope(scope => {
  scope.setExtra('battery', 0.7);
  scope.setTag('user_mode', 'admin');
  scope.setUser({ id: '4711' });
  // scope.clear();
});

Doesn't feel as nice as the Raven setup. I suggest wrapping Sentry in a client so you can set tags, userContext etc as you send the error.

[Nabellaleen]

Yeah, I've sound the same solution, but indeed, it's less sexy

            Sentry.withScope(scope => {
              scope.setExtra("state", state)
              scope.setExtra("data", data)
              Sentry.captureException(data.exception)
            });

[smilexu]

setExtra might be the workaround, but you need to clear extra, that is annoying.

[kamilogorek]

And we can't go back to previous Raven version due to CDN issues ...

@Nabellaleen what issues exactly?

Docs on scopes: https://docs.sentry.io/learn/scopes/?platform=browser

setExtra might be the workaround, but you need to clear extra, that is annoying.

You don't need if you use withScope.

I suggest wrapping Sentry in a client so you can set tags, userContext etc as you send the error.

You can still achieve this with mentioned withScope with ease.

There're a lot of reasons why we changed API. But it basically allows us to use event processors and handle states more efficiently in complex apps.

[smilexu]

@kamilogorek thanks, I will try with withScope

[kamilogorek]

I believe main issue was resolved. Feel free to let me know if it should be reopened.

[rhyek]

I think the new withScope is kind of pointless since you can't use async functions with it, apparently. You pretty much have to have the withScope and captureException very close to each other and you know what would solve that? If captureException accepted a scope parameter! @kamilogorek

[kamilogorek]

You can if you use promises the client directly, as we return async function from capture calls internally – #1449

If captureException accepted a scope parameter!

We've been there already and it was very hard to maintain and extend.

There're a lot of reasons why we changed API. But it basically allows us to use event processors and handle states more efficiently in complex apps.

[emmya]

Hello in 2019. It's SO ANNOYING that I can't just pass context as the second parameter in captureException. Please consider changing this.

If anyone came up with an elegant workaround/wrapping method please post!

[emmya]

😐😐😐😐😐😐😐

docs