Access and use Performance Risks inbox

You can access and use Performance Risks inbox to proactively identify and resolve application performance issues before they impact your end users. This guide will walk you through how to access the Performance Risks inbox, update the detection thresholds, and utilize the tool effectively within New Relic MCP server. For more information about what Performance Risks inbox is and its key benefits, refer to introduction to Performance Risks inbox.

Access the Performance Risks inbox

You can access the Performance Risks inbox at account and entity-level:

• Access at entity-level
• Access at account-level

Access at entity-level

You can access the Performance Risks inbox for a specific entity to view performance issues related to that entity and its associated telemetry data. This allows you to focus on the performance of a particular application or service and understand how it may be impacting your end users.

To access Performance Risks inbox for an entity:

1. Go to one.newrelic.com > All capabilities > APM & Services.
2. Select the required entity.
3. In the entity navigation pane, click Performance Risks in the Triage section.

Access at account-level

You can also access the Performance Risks inbox at the account level to get a holistic view of performance issues across all entities within your account. This allows you to identify common performance problems that may be affecting multiple applications or services and prioritize your optimization efforts accordingly.

To access Performance Risks inbox for an account:

1. Go to one.newrelic.com > All capabilities > Errors Inbox.
2. In the entity navigation pane, click Performance Risks.

View and analyze performance risks

Once you access Performance Risks inbox, you can view detected issues in two ways: the Triage view and the Group performance risks view. Both views display the same underlying data but offer different ways to analyze it.

Triage

The Triage view processes and groups similar performance risks together automatically. Similar queries are computed, stored, and merged into a single performance risk group. For example, multiple queries that share the same pattern — such as variations of an IN clause — are grouped into one entry rather than appearing as separate items. This makes it easier to identify and prioritize the most impactful problems without reviewing each occurrence individually.

Use the Triage view when you want a pre-grouped summary of performance issues to quickly identify patterns across your application.

Group performance risks

The Group performance risks view displays the raw performance risk data without pre-computed groupings. Normalized query representations (such as comma and question mark placeholders) are shown, and you can filter and group the data based on different attributes, such as:

• The user affected by the performance risk
• The service generating the calls
• The API triggering the queries

Use the Group performance risks view when you need to analyze performance risks based on specific attributes that are relevant to your investigation.

Set the thresholds

Performance Risks inbox uses configurable thresholds to automatically detect performance anomalies. You can update these thresholds at both the account and entity levels to ensure that the detection criteria align with your specific performance monitoring needs and priorities. These thresholds determine what constitutes a performance risk and help to ensure that you are alerted to the most relevant and actionable performance issues in your applications.

You can set the Performance Risks thresholds at an account or entity level:

• Account-level thresholds
• Entity-level thresholds

Set the account-level thresholds

Setting thresholds at the account level allows you to establish default performance risk detection criteria that apply across all entities within the account. This is useful for maintaining consistent monitoring standards and ensuring that all applications are evaluated against the same performance benchmarks.

To set the thresholds at an account level:

Set the entity-level thresholds

Setting thresholds at the entity level allows you to customize performance risk detection criteria for specific applications or services that may have unique performance characteristics or requirements. This is particularly useful for tailoring monitoring to different types of applications, environments, or business priorities.

To set the thresholds at an entity level:

You can set the thresholds for a specific entity in one of the following ways:

Use the Performance Risks inbox tool in New Relic MCP server

You can also access the Performance Risks inbox tool (list_performance_risks()) in New Relic MCP server. This tool lists all the Performance Risks detected for a given entity, along with their details such as risk type, severity, and occurrence count. You can use this tool to programmatically retrieve performance risk data.