Feature Request
Automatically tag unhandled exceptions in Raygun4Net
Current Status:
Completed
madd0
When using RaygunClient.Attach(string apiKey) the different clients attach to the platforms' different unhandled exception events and sends those exceptions automatically to Raygun.
Because this is all automatic, I can hardly distinguish these errors form errors that I'm sending manually. I think it would be a nice feature to be able to tag these errors with a user-supplied tag (e.g. 'FATAL').
Attach(string apiKey) could become (or have overloads) similar to Attach(string apiKey, IList
Raygun
Jason Fauchelle
Posted on
Jun 04 2014
Hello
Thanks for the suggestion! We will most likely add this feature in a future version of the Raygun4Net provider, though I can not currently say when. We'll let you know when this is available.
-Jason Fauchelle
madd0
Posted on
Jun 05 2014
Do you accept pull requests? :)
Raygun
Jason Fauchelle
Posted on
Jun 05 2014
We sure do. If you open a PR we'll certainly be able to get this feature in sooner than later.
alpriest
Posted on
Oct 24 2014
+1 it would be very useful to specify a default set of Tags when calling Attach (e.g. platform) so we can filter by iOS/Android in the reports.
Raygun
Jason Fauchelle
Posted on
Oct 24 2014
Hello,
One small issue with this request is to decide the behaviour of when the default tags get sent. The original request suggests that the default tags would only be used for reports that are sent automatically, so that they can be distinguished from reports that are sent manually. But you've pointed out another good but different use-case where you'd want default "Android" or "iOS" tags to be included with both automatic and manual reports.
One way for this to work both ways is for the basic Send method to report any specified default tags, and then the Send overload that takes tags could use the specified tags parameter and ignore the default tags. But then some people may want default tags to be included with manually sent tags.
We'll have a think about this, and any further feedback would be great.
Another solution that is available right now is to attach an event handler to the RaygunClient.Current.SendingMessage event. In this event handler, you can modify the e.Message.Details.Tags value. This will let you set "Android" or "iOS" tags for any message being sent to Raygun - both automatic and manual. This also give you control of whether you want to append the tag(s) to the list, or override any manually specified tags.
Raygun
Zheng Li
Posted on
Dec 09 2021
Hi All,
Exciting update in the app today, we've improved the UX and visibility of handled vs unhandled exceptions inside Raygun Crash Reporting.
"Unhandled" is now a configurable filter inside Crash Reporting. To use this filter, simply click on "Add filter" at the top of the Crash Reporting chart and choose "Unhandled" is equal to true/false to filter your exceptions below based on this criteria.
If the filter is set to "true", this page will only show you unhandled exceptions, if the filter is set to "false", this page will only show you handled exceptions and if you don't use this filter, it will show you both unhandled and handled exceptions.
This feature is now available for the following SDKs/providers:
- .NET
- JavaScript
- Apple
- ReactNative
- Node.js
- Xamarin
- Java
- Android
We are hoping to update the rest of the remaining providers by Q1 2022.
On a related note, we are also looking to improve the usability and user experience of our filters/search and sort capabilities for all our products. If you have some feedback you'd like to share with us in this area, then please let us know by using the "Contact Raygun" link in the sidebar of your Raygun app and mention "product feedback" in your comments.
In the mean time, please give this filter a go and let us know what you think!
Happy coding!
Zheng Li
VP of Product
Raygun