New Relic can show an alert, an incident, an APM application, a dashboard, or the output of an NRQL query. Strawberry can bring those verified sources together with the browser context you select to prepare an incident or performance brief that engineering can inspect.
01
Start an incident with the evidence in one place.
An incident review should begin with the current signals, not a manual hunt through separate views. Strawberry can list incidents and alerts, retrieve the relevant dashboard, and gather the selected supporting context into a concise engineering brief.
02
Ask a precise question of the telemetry.
NRQL is most useful when the question and interpretation are both explicit.
Strawberry can run an approved NRQL query and present the result beside its scope, while the engineer decides what the measurement means.
03
See the service behind the symptom.
A dashboard spike matters differently when the affected APM application, recent release, and current incident are visible together. Use the connected New Relic account and selected tabs to prepare a source-linked investigation path.
04
Make the health review arrive prepared.
Teams can save a stable review as a skill that lists the same alerts, incidents, dashboards, applications, and query checks each time. A routine can build that agenda on schedule for the on-call lead.
New Relic Strawberry