capturing a message with stack trace using @sentry/browser

[samuelcolvin]

• 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:

raven-js:        3.26.4
@sentry/browser: 4.1.1

Description

I'm switching from raven-js to @sentry/browser.

In raven-js I could do

Raven.captureMessage('whatever', {
    stacktrace: true, level: 'warning', extra: extra_info
})

However with @sentry/browser captureMessage only takes a level argument. To add extra I can use

Sentry.captureEvent({
    message: 'whatever',
    level: 'warning',
    extra: extra_info
})

(which is arguably uglier), but the real problem is that there's no way to add stacktrace: true, instead the stacktrace argument requires an actual stack trace. I tried settings stacktrace: true but I got "Discarded invalid value for parameter 'stacktrace'".

It doesn't seem to be possible to log a message with a stack using @sentry/browser.

[HazAT]

There is an option called attachStacktrace for init see: https://docs.sentry.io/learn/configuration/?platform=browser#attach-stacktrace

After that you call captureMessage and you will get a stacktrace.

[samuelcolvin]

(github is still being a pain, so I can't see your message except in emails.) That's useful, thank you. Would still be useful to decide whether to include the stack trace when firing the message.

…

On Mon, 22 Oct 2018 at 14:39, Daniel Griesser ***@***.***> wrote: There is an option called attachStacktrace for init see: https://docs.sentry.io/learn/configuration/?platform=browser#attach-stacktrace After that you call captureMessage and you will get a stacktrace. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1666 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD2jGZ_upB1fl6QnH5X8yZnQeNCuuPhlks5uncqBgaJpZM4XzFhf> .

[HazAT]

While attaching a stack seems simple, it actually adds a overhead to performance and payload.
In regards to capturing any extra data with an event, you can do it either by using configureScope or withScope see: https://docs.sentry.io/learn/scopes/?platform=browser

Also if this seems not to be enough you can write your own integration.

[samuelcolvin]

Thanks for the response, I'll close this however IMHO it still seems like a step back from the raven-js interface.

[kajirikajiri]

https://docs.sentry.io/platforms/javascript/configuration/options/#attach-stacktrace

This issue appears at the top of a Google search for sentry capturemessage stacktrace.
Since the reference link is Page Not Found, the latest attachStackTrace link is included.

There is an option called attachStacktrace for init see: https://docs.sentry.io/learn/configuration/?platform=browser#attach-stacktrace

After that you call captureMessage and you will get a stacktrace.

[adrian-skybaker]

There is an option called attachStacktrace for init

Not ideal as this doesn't let you include for just some messages, and the overhead involved means it's likely undesirable to enable it for all messages.

[mydea]

If you only want it for specific messages, I'd suggest to just use Sentry.captureException(new Error('my message with stack'), { level: 'info' }), or something along these lines.