Integrations / NewRelic
NewRelic
New Relic application performance monitoring platform
API key
Indexes
Actions
What Telara does
Capability matrix
Before you connect
Prerequisites
A New Relic account you can administer.
The account ID for the account Telara should read.
Vendor setup
Get the credential
1
Create a user key
In New Relic, open API keys. Create a User key (not an ingest license key, and not a browser key).
2
Paste in Telara
Settings → Integrations → New Relic. Enter the user key and the account ID.
In Telara
Connect in Telara
API key
In Telara, open Settings → Integrations, choose this connector, and paste the key into the fields Telara shows.
Fields Telara asks for
- API key
- Account ID
Knowledge
What gets indexed
| Resource | Coverage |
|---|---|
| Application | Partial — not every record the vendor holds is synced |
| Alert | Partial — not every record the vendor holds is synced |
Sync
Freshness & sync
| Resource | Lag | Deletions |
|---|---|---|
| Application | Up to 1 day | Removed records disappear on the next full sync |
| Alert | Up to 1 day | Removed records disappear on the next full sync |
Data handling
Permissions & data handling
Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.
Excluded from semantic search: Application, Alert.
After connect
Verify it worked
After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.
Honesty
Known limitations
Ingest license keys cannot read the APIs Telara uses. That mismatch is the most common failed setup.
Account ID must be the account that owns the key. A parent/child mix-up looks like a permissions error.