New Relic

Liddr reads your observability state — open and recent alert violations, incidents, APM deployment markers, and the entity catalog (applications, browser apps, synthetic monitors) — so Know can answer "what's broken / what shipped" and Signals can surface incidents as risks. Liddr never writes to New Relic; the key only ever needs read access.

What Liddr accesses

Direction	Access
Ingest (read into your knowledge graph)	Read-only
Reverse sync	None — Liddr never writes to this source

Setup

1. In New Relic: one.newrelic.com → your profile → API keys → Create a key of type User (NRAK-…). License/Ingest keys won't work — the REST API requires a User key.
2. Create it on a dedicated user with a read-only role — the key carries that user's account permissions.
3. In Liddr: Settings → Connections → New Relic, paste the key; in Advanced settings set Region to eu if your account is EU-hosted (default us), and optionally the Account ID and ingest window.
4. Test, then run an Ingest.

Required scopes

User API key

Ingest — minimum

• No key-level scopes — access follows the key owner's account role
• A read-only (or Basic) user role is sufficient for everything Liddr reads

TIP

Read-only is both the minimum and the maximum — there is no reverse sync to New Relic. Don't mint the key on an admin user, and don't paste a License or Browser key by mistake (they authenticate data ingest, not the read API).

Reference

• New Relic docs: API keys