In the Errors Dashboard you can view an Error Detail page to get a more thorough and in-depth look at both recurring errors and individual errors. The information about all the errors you gather here will be helpful for diagnosing why your app is not working as planned. Read below to see the features of Error Details.
You can get to the Error Details page for recurring errors by clicking on the "View all Occurrences" link as shown below. This page will display a graph of the errors that keep recurring. It will also display details on the last error that occurred such as the Location, Stack Trace, and Http Request.
By clicking "Resolve" this particular error will be listed as a Resolved error in the Error Dashboard page unless it recurs. If it does recur, the error would then be categorized as a Regressed error. This is especially helpful for troubleshooting your app because you will be able to see which errors are fixed and which one are recurring and need to be fixed.
You can ignore (and later un-ignore) a group of errors. This is especially helpful when not wanting a certain type of exception to show up in the dashboard and create unwanted noise.
Under the “Occurrences” tab you will be able to see a list of individual errors and the corresponding error message along with when and where the error took place. Here you can select an individual error for further investigation.
You can look at an individual error by clicking an exception message listed in the Errors Dashboard. When looking into an individual error as opposed to the occurrences of a recurring error, a window will be open to help you pinpoint you to the source of the exception. In this window you can view all occurrences of an error which will take you to the page covered earlier. There are also two tabs available that will tell you different things about an individual error: “Details” and “Logs”.
Along with the Error message, you can capture additional information in this window. If configured, Retrace will retrieve information about a current http request such as POST data, Query strings, Server variables and others. To pull this information and list it in the Error Details page for .NET apps, you will want to add the following keys into the appSettings section of your App/Web.config:
<appSettings> <add key="Stackify.CaptureErrorHeaders" value="true" /> <add key="Stackify.CaptureErrorPostdata" value="true" /> <add key="Stackify.CaptureServerVariables" value="true" /> <add key="Stackify.CaptureSessionVariables" value="true" /> <add key="Stackify.CaptureErrorCookies" value="true" /> </appSettings>
To learn how to get Web Request details for your Java Apps, see the article titled Java Servlet Filters.
The Logs tab will take you to a window that will show the error in context with the app's other logging messages. You can easily pull in more messages to see what was happening before the error occurred or select "view more" to be brought to the Log Dashboard where you can get a better view of the error in line with your other logging statements.
Sharing a Link
You can copy a link of an error exception. This link will allow any Stackify user to view that particular exception details page.
Sharing Through Email
You can also email the exception to a member of your team. This email will include the error details along with the link to view more about the error in Stackify.
Using the JIRA Integration
After properly configuring the Jira Integration, you will be able to send Stackify errors directly to Jira cloud. These Stackify errors will automatically be associated in Jira as a work item and can be assigned an issue type and priority level.
Using the TFS Integration
After properly configuring the TFS integration, you will be able to send Stackify errors to TFS.
Using Axosoft Integration
After properly configuring the Axosoft integration, Retrace users can export the error to Axosoft. Select the appropriate options on the form, fill out the summary, then click 'Create' to send your error to Axosoft for tracking!