Engineering integration guide
New Relic + UbiGrowth workflows
New Relic is an observability platform covering application performance, infrastructure, and incident context. This guide covers the records that matter, how the connection should be scoped, and what the first bounded workflow should be.
Introduction
Make New Relic part of the workflow, not another silo.
Validate connector availability for your workspace
This guide covers how a team designs a engineering workflow around New Relic with UbiGrowth: which records stay authoritative, how the connection should be scoped, what the first bounded workflow should be, and how to tell whether it worked.
The records that matter are Entity, Transaction, Error, Alert Condition, Dashboard, Workload, and NRQL Query. New Relic identity is the Entity GUID, and entities are discovered from telemetry. An instrumented service that stops reporting eventually stops being an entity, which breaks alerts that referenced it.
New Relic is not currently on UbiVibe's verified connector list. This page is an implementation design reference: use it to specify the workflow, then validate whether the connection is available and correctly scoped for your workspace before you make it a dependency. The verified UbiVibe connections today are Salesforce, HubSpot, Gmail, Google Drive, Slack, and GitHub.
The platform layer is the usual destination for this connection, because the value shows up as governed context and execution shared across more than one team.
Why teams evaluate this connection
Integrations create value when they remove operating friction.
The first design decision is not which API endpoint to call; it is which system owns the record, what event should trigger work, who owns the exception path, and what successful completion means.
Engineering systems produce more signal than any other part of the business and the least usable summary. New Relic knows exactly what happened; turning that into something the rest of the company can act on is manual work that nobody owns.
The second problem is direction of risk. An integration that reads engineering activity is low-risk and useful. An integration that can act on infrastructure or production systems is a different category entirely, and the two are often discussed as if they were the same project.
You're likely here because
- Engineering activity is invisible outside the engineering team
- Incident context has to be reassembled manually every time
- Internal tool requests sit behind product work indefinitely
Record model
What a New Relic integration actually reads and writes.
Integration design starts from the objects the system really exposes, not from a generic connector diagram. These are New Relic's.
Identity and matching
New Relic identity is the Entity GUID, and entities are discovered from telemetry. An instrumented service that stops reporting eventually stops being an entity, which breaks alerts that referenced it.
Start here
Run one NRQL query for the transactions that carry business meaning and alert on their outcome rather than on host metrics.
What this will not do
It will not replace application logging. APM samples; the specific failing request may not be in the sample.
The constraint to plan around
Data retention differs by telemetry type and account tier, so a query that works over a week fails silently over a quarter by returning a truncated window.
Build notes
What you actually have to reason about in New Relic.
The fields that carry meaning, how the connection authenticates, and whether the event surface can be trusted. This is the part that decides whether the integration works in month three.
| Field | Why it matters |
|---|---|
| entity GUID | the stable handle, though entities are discovered from telemetry and expire when it stops |
| appName | the grouping key, and two deployments sharing a name merge into one entity |
| transaction name | the unit of performance analysis, and high cardinality here degrades everything |
| NRQL time window | retention differs by data type, so a long query silently truncates |
| error class / message | the grouping inputs for error analysis |
Authentication
User key for queries and NerdGraph, licence key for ingestion, and they are not interchangeable. Keys are region-bound between US and EU accounts, which is a common first failure.
Events and delivery
Alert conditions fire to notification channels and webhooks. There is no general change feed — you query telemetry rather than subscribe to it.
Workflow
How the New Relic workflow runs.
The operating sequence, from reading the source system through to the result landing back where it belongs.
Step 01
Connect read-only first
New Relic is connected with scoped, read-only credentials so context and reporting value can be proven without any action risk.
Step 02
Assemble the engineering picture
Delivery, incident, or operational activity is summarized in a form the rest of the business can act on rather than a raw feed.
Step 03
Build the internal surface
Launch produces the dashboard or internal tool that was never going to clear the product backlog, reviewed like any other internal service.
Step 04
Bound any action path
If the workflow needs to act, that path is specified separately with explicit scope, approval, and a record of what ran.
Design decisions
The engineering decisions this connection forces.
Each of these has to be settled before the New Relic workflow is allowed to write anything.
Step 01
Separate read from act
Reading New Relic for context and reporting is a different risk decision from letting a workflow act on it. Do not bundle them into one project.
Step 02
Make execution paths explicit
Any action that reaches a real environment should run through a reviewable execution path with a record of what ran, not an implicit side effect.
Implementation path
How to implement the New Relic workflow.
- 01
Start read-only against New Relic and produce something the team already wants: delivery visibility, incident context, or an operational summary.
- 02
Use scoped credentials rather than a shared token, and confirm what the scope can actually reach.
- 03
Build the internal surface in Launch, and review the result as you would any other contribution.
- 04
Once business-transaction alerting works, retire host-level alerts that never correlate with customer impact.
Governance
Controls that matter.
Control 01
Credentials are scoped and workspace-approved; no shared secret belongs in a prompt or in generated code.
Control 02
Actions that reach production systems run through explicit, reviewable execution paths.
Control 03
Generated code and configuration are reviewed on the same terms as any other change.
Failure modes
How a New Relic integration breaks in production.
Not generic integration advice. These follow from how this system actually behaves, which is why they look nothing like the list on the next guide over.
Symptom 01
Alerts reference an entity that no longer exists.
Cause
Entities are discovered from telemetry and expire when reporting stops.
Fix
Alert on absence of telemetry as its own condition rather than relying on entity-scoped conditions.
Symptom 02
Two deployments merge into one entity.
Cause
They share an appName.
Fix
Distinguish by environment and version attributes at instrumentation time.
Symptom 03
A quarterly query silently returns a shorter window.
Cause
Retention differs by telemetry type and truncated the range.
Fix
Check retention for the data type and state the actual window on the output.
What changes at scale
Ingest is billed by volume and query concurrency is capped. Dashboards with many widgets on auto-refresh hit the concurrency cap before they hit any data limit.
Examples
What a working New Relic workflow looks like.
Bounded scenarios rather than a feature list. Each one can be verified against work the team already does.
Observability workflows
With New Relic connected read-only, delivery and operational activity can appear alongside commercial context instead of living in a separate report.
Internal tool that was stuck in the backlog
A small tool reading New Relic gets built in Launch and reviewed like any other internal service, without consuming sprint capacity.
Limitations and considerations
What to validate before you depend on this.
- Data retention differs by telemetry type and account tier, so a query that works over a week fails silently over a quarter by returning a truncated window.
- Ingesting high-cardinality custom events or attributes drives cost and degrades query performance for everyone on the account. The data cannot be un-ingested.
- When application-level logging would answer the question. APM samples, and the specific failing request is often not in the sample.
- Write or action access to New Relic is a materially different risk decision from read access and should be scoped, reviewed, and approved separately.
- Generated code and configuration still require review. Speed of production does not change ownership of what ships.
FAQ
New Relic integration questions.
What records does a New Relic integration actually work with?
The primary records are Entity, Transaction, Error, Alert Condition, Dashboard, Workload, and NRQL Query. New Relic identity is the Entity GUID, and entities are discovered from telemetry. An instrumented service that stops reporting eventually stops being an entity, which breaks alerts that referenced it.
What should the first New Relic workflow be?
Run one NRQL query for the transactions that carry business meaning and alert on their outcome rather than on host metrics.
What will a New Relic integration not do?
It will not replace application logging. APM samples; the specific failing request may not be in the sample.
What is the main constraint to plan around?
Data retention differs by telemetry type and account tier, so a query that works over a week fails silently over a quarter by returning a truncated window.
What changes about a New Relic integration at scale?
Ingest is billed by volume and query concurrency is capped. Dashboards with many widgets on auto-refresh hit the concurrency cap before they hit any data limit.
How does authentication work for New Relic?
User key for queries and NerdGraph, licence key for ingestion, and they are not interchangeable. Keys are region-bound between US and EU accounts, which is a common first failure.
Does New Relic support webhooks, and can they be trusted?
Alert conditions fire to notification channels and webhooks. There is no general change feed — you query telemetry rather than subscribe to it.
What is the risk of writing to New Relic?
Ingesting high-cardinality custom events or attributes drives cost and degrades query performance for everyone on the account. The data cannot be un-ingested.
When is connecting New Relic the wrong call?
When application-level logging would answer the question. APM samples, and the specific failing request is often not in the sample.
What should a New Relic integration automate first?
Start with one bounded workflow that removes a measurable handoff, duplicate-entry step, reporting delay, or follow-up gap. Expand only after the first workflow is reliable.
Does UbiGrowth require New Relic to be replaced?
No. The operating model is designed around connecting to systems that should remain authoritative and building workflows around them rather than forcing a wholesale replacement.
Is connector availability identical for every workspace?
No. Availability can depend on provider configuration, authentication, scopes, workspace setup, and deployment state. Validate the required connection before treating it as an operational dependency.
Can the workflow act on New Relic, not just read it?
Action paths are possible but should be treated as a separate, bounded project with scoped credentials, explicit approval, and a record of what ran.
How are credentials handled?
Through workspace-approved, scoped grants. A shared secret pasted into a prompt or embedded in generated code is not an acceptable pattern.
What is a safe first integration?
A read-only workflow that produces something the team already wants from New Relic — delivery visibility or incident context — before any action path is considered.
How this access is governed
What ARIA is allowed to do in New Relic, and who decides.
Connecting New Relic is a permission decision, not just a setup step. These are the controls that decide what ARIA can reach, what it can change, what gets recorded, and how you take the access back.
Required permissions
ARIA works through the scopes the connection was granted, and no others. Authorization happens at the provider, so the permissions being requested are shown by the system itself before anything is connected.
What it can reach
Reachable systems are the intersection of what your organization approved in the connector registry and what the requesting identity is permitted to use. Identity resolves before execution, not after.
What it can do
Actions run through explicit execution paths with state, spend, and failure boundaries — a bounded worker path rather than an open-ended agent loop with a credential.
Credential handling
Credentials live in the governed connection layer and are resolved through canonical connection identity. They are not pasted into individual workflows, prompts, or generated artifacts.
Action logging
Execution carries state and traces: what triggered the work, which connection it used, and what came back — including an explicit failure when something did not run.
Approval and revocation
Consequential actions can be made to require a person to approve them. Access can be changed or revoked at the connection, and ARIA loses that reach without unpicking the work already completed.
Start with ARIA
Ask ARIA to run this integration.
Describe the outcome you need across this system. ARIA works out the scopes, data, and actions the job requires, and operates inside the access you grant — which you can change or revoke.
- ARIA acts only through the systems and permissions you connect.
- Connections use scoped credentials you can change or revoke.
- Actions are recorded, and consequential ones can require approval.
Start here
Turn the integration into a working business outcome.
Start with ARIA to describe the outcome, then continue into the product path that fits the workflow. Connector availability and required scopes should be validated for the specific workspace before production use.