After closer review this may not be possible to do the way you requested it.
Notification is send only for new crash. As you know new crash is based on the hash created from crash report fields. Custom Field data are not used to generate the hash so you may have multiple users generating the same crash. We can send any Custom Field data in the notification but this will be misleading as what you really get is data from the first report that generated this new crash notification.
That sounds perfect, thankyou!Andrew Beveridge shared this idea ·
Just had an additional thought that perhaps as an alternative to defining a list of "developer devices", it would be useful to be able to define IP ranges which should be classed as "developer crashes".
In this case we'd define office IP range, so developer testing would always be tagged and easily identifiable.
This would be really helpful! The ability to differentiate between DEBUG and RELEASE builds is great, but even when testing the RELEASE build of our app (e.g. from the Play Store), we're likely to get a higher number of crashes from devices owned by the company for internal use.
It would be really useful to be able to exclude / filter these out by defining a list of "developer devices" which could be identified by IMEI/Serial or other unique identifier.
I like this idea with applying tags to crash reports. I also see it as a quite complex feature. We will try to break it into smaller parts so you can enjoy it as soon as possible.
I agree this would be really useful; the ability to define rules (for example like filters in gmail) which add tags to reported errors would help a lot.
These rules could be applied whenever a new crash report comes in to the collector to automatically apply tags based on string/pattern matching.
If we could also then filter by those tags easily, this would satisfy one of my other requests for a "developer device" whitelist / filter, because we could instead just create a filter which searched for any of our developer device IMEIs in the crash report and gave them a "Dev" tag which we could then filter out.Andrew Beveridge supported this idea ·