When you view an anomaly, you can inspect:

• Business Transaction snapshots from the time period of the anomaly.
• Actions executed as the result of policies you have configured for the Business Transaction.

These are options of the standard troubleshooting flow. They are typically done as follow-up.

In this example:

• Suppose we want more context for the Process CPU Burnt issue on PaymentService1. We can view snapshots of transactions affected by that issue. Double-click a snapshot in the list to open it in its own pane, and if desired, drill down into details and call graphs.
• It is common to send messages to a ticketing system when an anomaly occurs. In this case, we posted to Slack, for our Ops team to see that on their phones.