Feature Request
Ability to export exceptions
Current Status:
Completed
samwho
It would be nice to be able to export error data so we can process it locally and pull useful data out of it, rather than having to page through hundreds of thousands of occurrences of the same error.
Raygun
John-Daniel Trask
Posted on
Aug 16 2013
Hi,
Interesting idea, I guess we could generate our raw JSON feed from it.
More ideally though, I'd like to understand what sort of slicing and dicing you want to do. If it would help everyone in solving problems perhaps it would be best if we simply added those tools to Raygun to help everyone out!
We are at present adding support for aggregate data (e.g, you have an error group, what browsers does it impact? So you might see that a JS error is only occurring on IE, so you know how to more easily fix that rather than paging through instances to understand that it's only impacting IE).
Appreciate your feedback,
John-Daniel Trask
Co-founder
Mindscape
samwho
Posted on
Aug 16 2013
Hi John,
We have an error that has occurred a few hundred thousand times. The errors contain unique database item IDs in them so we can investigate what bit of data caused the problem. Instead of going through each error one by one, it would be helpful to be able to export the data, extract all of the IDs and then do our own aggregation to help debug the problem.
I know that's a rather abstract explanation of our problem, but does it answer your question? :)
Thanks, Sam
kevman
Posted on
Feb 16 2014
Additionally the ability to export would in my opinion be beneficial to include for decision makers, giving them some confidence that the platform does not lock them in without options in the future.
jiggstrom
Posted on
May 12 2015
We have the exact same problem, that data contains database-id:s that we some times have to work through to fix something after an error occured.
It is allmost impossible to predict i beforehand what kind of aggregation you would like when you are asked to report something or investigate sideffects of an outbreak.
Kosta Tenedios
Posted on
Apr 07 2016
At the company I work for we would like to be able to extract all of the data so that we can perform our own trend analysis as well as correlate the data with other data we collect (e.g. application analytics). That way we can get a holistic view of the quality of our software and better prioritise our efforts in improving application quality.
Brent Taylor
Posted on
Jul 08 2016
We are tracking errors that we would like to be able to export the error type, counts, browsers, and IP addresses of the user that had the error in bulk instead of paging through the errors and accumulating data by hand.
We are capturing 1000s of Denial of Service and Script Injection attacks as errors and would like to be able to filter those users and report on them to our management. Trends and periods of high activity etc...
Yosan
Posted on
Aug 12 2016
Hi,
I'm pleased to say that in a few weeks the ability to export exceptions will be available.
There will be two ways you will be able to export exceptions:
- By error group
- All error groups within a time range
The format will be the JSON payload of each error, in a zip file.
We'll let you know when the feature is live. Thanks for your feedback and suggestions :)
Kind regards,
Yosan
Raygun
Zheng Li
Posted on
Sep 27 2016
Hi all,
The bulk export feature is now available for Raygun Crash Reporting, you can learn more about it here: https://raygun.com/blog/2016/08/feature-release-export-functions/
Please note: The Crash Reporting bulk export feature is only available to Business and Enterprise plans only. All plan types already support the ability to export individual error instance from Raygun.
Regards,
Zheng