With Coderr you get an overview of all errors generated in your application, their type and cause. Coderr provides relevant information attached as context with the error. The analytical tool lets you weigh the impact of the different errors which makes prioritization easier.
Coderr detects errors through constant monitoring of your application. When an error occurs, Coderr will provide a notification straight away. By starting to correct issues immediately, it is possible to prevent users from experiencing the same error and maintain the availability of the application.
Coderr’s capability of finding bugs in development and test environment and not only in production means you have a comprehensive view and can prioritize your code improvements. There are opportunities to find solution options through error codes and links to solutions already tried by others. In Coderr you will track how the amount of errors vary with different versions of the application, leading to improved code quality.
The overview is central to getting a quick view on what is going on with your application or applications, if you have multiple as shown in the example above. Instead of having a control board rich with capable features and functions, the new overview has given way to relevance and clarity. To the left, there is a summary of your different incidents and in center the graphical display provides a clear view of variation over time. Both parts are organized in time intervals that you can set yourself.
Different functions of Coderr are organized in a logical flow. From the overview under "Discover", one would typically want to find out more about what has occurred in the application. In “Analyze” there are further details per each incident where the rich context will provide necessary information for further decision and actions.
With Coderr, programmers do not need to add additional code, like log lines, to get relevant information that tells why an error was generated. Coderr collects information automatically without cluttering the code base.
Applications can generate many incidents so it is essential to prioritize the work dealing with them. The criteria, or your business rules, can be set to reveal the errors that are the most frequent or oldest. But you can also use criteria which affects most users and easily define your own criteria. Using criteria for prioritizing the incidents bring structure and consistency for everyone involved in application development or performance.
Deployment Insights reveals how earlier changes compare with number of incidents. Are the number of unique errors getting fewer or are they increasing per version? This view show trends in number of errors per version release and if code quality seems to be improving.
In addition, Deployment Insights also provide specific information about the errors per version release. Here you can discover if older errors resurface again or there are new different kinds of errors relating to the specific version release which need attention.