Sentry-react-native: Tag for where crash originated

Created on 27 May 2020  路  5Comments  路  Source: getsentry/sentry-react-native

Motivation

Currently, it's hard to tell/filter in Sentry where a crash originated.
Did it occur in JS, iOS/Android or even NDK?

We send already a bunch of tags:
image

One new tag we should add is crash.origin
With a few potential values:
javascript
ios
android
ndk

to be able to filter events in the Sentry UI for exactly just those crashes.

Feature Request

Most helpful comment

Two suggestions:

  1. not having either android or ndk but having always android and a second tag to mark ndk. This way one can filter all Android events (regardless if from Java/NDK).

  2. Tag the SDK name instead?

sentry.javascript.react-native
sentry.cocoa
sentry.java.android
sentry.native

All 5 comments

Two suggestions:

  1. not having either android or ndk but having always android and a second tag to mark ndk. This way one can filter all Android events (regardless if from Java/NDK).

  2. Tag the SDK name instead?

sentry.javascript.react-native
sentry.cocoa
sentry.java.android
sentry.native

liked @bruno-garcia s idea, so one can filter on a high or low level.
tag's name could be event.origin instead of crash.origin as not every event is a crash.

I agree with event.origin over crash.origin and did actually implement that in the commit. Didn't mention it here, my bad.

@jennmueng can we close this? #890 is released

Yes!

Was this page helpful?
0 / 5 - 0 ratings