Track releases and regression fixes
Connect
SPIRITT
New RelicNew Relic
From signals to fixes
SPIRITT builds dashboards, configures alerts, and investigates release impact using your New Relic telemetry. It carries the findings into owned engineering work and checks whether fixes improve service health.
What you can do with New Relic.
Release decisions with evidence
Compare deployment markers with response times, throughput, and errors to separate release regressions from changes in traffic.
Alerts with a destination
Create alert policies and conditions, route them through AI Notifications workflows, and test the destinations and channels that reach your team.
Reliability work that closes
Turn telemetry into engineering tasks, attach the evidence, and query New Relic again after fixes to verify the outcome.
Works with your other apps.
Get started in three steps.
01
Open your workspace
Start a SPIRITT workspace for release checks, service reliability, or the observability operation you want to delegate.
02
Connect New Relic
Connect New Relic with an API key that has access to the accounts, telemetry, and configuration changes your mission needs.
03
Delegate an outcome
Give SPIRITT your services, reliability targets, and team ownership rules. It builds the workflow and carries the work through verification.
Hand over a mission.
Choose a mission. Make it yours.
Put New Relic to work.
Put reliability work in motion
Questions
New Relic, with SPIRITT.
01What can SPIRITT create or change in New Relic?+
SPIRITT can create dashboards, add widgets, create deployment markers, add entity tags, define service levels, and configure alert policies and supported conditions. It can also query telemetry with NRQL and send custom events or trace data for systems it operates.
02What access does the connection need?+
New Relic connects with an API key. Its account access and permissions must cover the mission: querying telemetry, creating dashboards, and configuring alerts can require different access. SPIRITT works within that access rather than assuming every connected account is writable.
03Can SPIRITT check releases automatically?+
Yes. A recurring workflow can combine confirmed deployment records with New Relic deployment markers, error data, and application metrics. SPIRITT compares defined windows and thresholds, sends the verdict to your team, and checks the same measurements after a corrective release.
04How does New Relic connect to engineering work in other apps?+
SPIRITT can carry alert violations, NRQL findings, and deployment context into Jira, Linear, or GitHub tasks, then coordinate owners in Slack. New Relic remains the telemetry source while the connected task system tracks investigation and remediation.
05What useful systems can SPIRITT build around this connection?+
Examples include a release verification console, a service ownership directory, an endpoint coverage register, and a batch operations app that sends custom events. SPIRITT can also create dashboards directly in New Relic, rather than requiring a separate interface for every mission.
06How is this different from a New Relic alert policy?+
An alert policy groups conditions used to detect problems. SPIRITT can configure those policies and build the surrounding operation: investigate telemetry, correlate deployments, create engineering tasks, coordinate owners, and verify recovery. It does not treat an alert or a coincident deployment as proof of root cause.