# How to use a Righthand with New Relic

Use Righthand to prepare a New Relic alert-routing review with issue context and responsible teams.

By Righthand Team · 2026-10-12

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-new-relic

## Quick answer

Use Righthand to prepare a New Relic alert-routing review with issue context and responsible teams. Notification delivery is distinct from somebody accepting the incident.

Start with a reviewable deliverable, keeping New Relic as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

New Relic documents alert conditions, issues, and Workflows for notifications. See the [official New Relic reference](https://docs.newrelic.com/docs/alerts/). Provider capabilities and Righthand's available tools are separate checks.

Scope the packet to the approved entity, environment, alert conditions, and supplied query results with exact windows and units. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: account, issue ID, condition, threshold, observed signal, workflow destination, assigned owner. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

A triggered condition does not establish the root cause. Keep notification edits and incident decisions with operations staff.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the operations owner |

## Illustrative first-run brief

> Use the owner-provided New Relic snapshot or approved read-only view. Compare the supplied issue list with approved routing rules. Flag missing owners and unclear destinations. Draft handoff questions without changing conditions or workflows. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the operations owner to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

An issue sent to a channel can still be unowned. The review asks who accepted responsibility rather than marking the handoff done.

Match an issue to its condition and configured notification destination. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Entity A | Matching query and window | Comparable summary |
| Chart B | Unit definition differs | Hold numeric comparison |
| Alert C | Cleared, path untested | Recovery still unknown |

## Common failure and recovery

A workflow change can make an old routing export inaccurate. Refresh the affected configuration before blaming an absent notification on staff.

If one chart uses a different entity or interval, hold the cross-chart conclusion and request matching source context from the observability owner.

## FAQ

### What should the reviewer verify first?

Verify entity ID, query, aggregation, unit, threshold, and time window. A service average may not establish the experience of a specific request.

### How should a repeat run be scoped?

Preserve entity and query definitions for repeat reports. Reopen comparisons after instrumentation changes and keep incident resolution tied to the owner's acceptance evidence.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.