Tag for where crash originated
See original GitHub issueMotivation
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:
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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Remove before flight - Wikipedia
Remove-before-flight components are often referred to as "red tag items". Typically, the ground crew will have a checklist of remove-before-flight items.
Read more >Crash Tag Team Racing - Regional Differences
This was the first game in the series to feature a different character model for Crash in Japan. Crash has the design used...
Read more >Trivia / Crash Tag Team Racing - TV Tropes
The basic concept originated with Traveller's Tales. Their version was called Crash Clash Racing, and it would have been a more immediate continuation...
Read more >Evil Crash | Bandipedia - Fandom
The initial origin behind the character was vastly different, as he was supposed to be Crash Bandicoot himself after undergoing a temporary mutation...
Read more >Instructions to Police for Reporting Crashes
TEXAS PEACE OFFICER'S CRASH REPORT (FORM CR-3) OVERVIEW ................. 12 ... 3.3.5 – LP STATE (License Plate State) .
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Two suggestions:
not having either
android
orndk
but having alwaysandroid
and a second tag to markndk
. This way one can filter all Android events (regardless if from Java/NDK).Tag the SDK name instead?
sentry.javascript.react-native
sentry.cocoa
sentry.java.android
sentry.native
I agree with
event.origin
overcrash.origin
and did actually implement that in the commit. Didn’t mention it here, my bad.