Raygun APM proactively curates a list of your app's biggest performance issues and displays them for you on the “Issues” page.
These issues are created due to the violation of known performance rules. Every time a transaction (trace/method/query/API call) violates a Raygun APM performance rule, an active issue is generated on the “Issues page”. Any subsequent sightings of the same rule violation by the same transaction will be grouped together under the same issue.
Each of the issues under the APM “Issues” page is a group of the same transactions that violated the same APM performance rule.
This article covers the following:
The issues are grouped based on the rule violation and the traces. Each issue group might have 1 or more traces. Each issue group can be clicked and viewed in detail.
Sorting your issue groups
You can sort the issues on the “Issues” page by clicking on a header row column. By default Raygun APM issues are sorted by last seen, but you can also sort by type, issue name, first seen or number of traces.
Just like Raygun Crash Reporting, Raygun APM lets you assign issue groups to one of five issue statuses. These are:
- Resolved In Version
- Permanently Ignored
Raygun APM's issue statuses and notification system work together to notify you of new and repeating issues, much like that of Raygun Crash Reporting.
Changing your issue status
When an issue is first received it is assigned to Active, and is visible in the first tab. You can then take action to change it to another status. This can be done in two ways:
- From the individual issue group view: when viewing the details for an issue group, click the top-right dropdown to assign this issue group to another status
- From the application view: when viewing all APM issues in an application, select one of the four status tabs, select one or many error groups using the checkboxes to the far left, then click the blue 'Change Status' button to assign them all.
After changing the status, the issue group will then be moved and visible in its new tab.
Effect of error statuses
When a new issue occurs, you will receive a notification email. If traces of this issue group continue to arrive, you will receive follow-up emails at certain time intervals (so we don't flood you with notifications for every trace).
The issue group is removed from active counts and the Raygun APM Daily Digest email. If another trace is received, the issue group will be reassigned to Active and a reoccurring notification will be sent.
Similar to 'Resolved' above, but the reoccurring email notification is different. This is useful to mark junk issue groups separately from your actually fixed issues, for instance when setting up Raygun and sending test transactions.
If you set an issue group to Ignored, the next time it receives a trace, you will get an email notification informing you it has reoccurred.
This removes the issue from all active count as above, but if a new trace arrives it will not be reassigned to Active. No notifications will ever be delivered again for this issue group, until you manually reassign it to Active from the Issues page.
If you do not want further issue to be created from a APM rule, you can mute, snooze or delete rules. This ensures that no more new issues will be created from the violation of that rule.
Create a manual issue
You can create manual issues (not originating from a rule violation) from a trace or method. Manual issues are labelled as “Manual” type on the Issues page.
From a trace or a method detail page
You can also create an ad hoc issue from a trace or a method detail page. Simply click on the “Add to issue” button on the top right of a trace or a method detail page and you can choose to create a new ad hoc issue or attach the trace/method manually to an existing issue.
From the Traces page
You can also manually create a new issue from traces or add them to an existing issue. Just select one or more traces on the “Traces” page and these options will become available to you.