You open an incident dashboard at 2 a.m., wondering who on earth approved that production change. The logs are a blur of service accounts and token IDs. You know the data came from New Relic, but where’s the source of truth? That’s where New Relic Veritas starts earning its name.
New Relic Veritas blends observability with verification. New Relic tracks your metrics, traces, and errors. Veritas ensures those signals tie back to known, trusted identities. Together they close the loop between “what happened” and “who did it,” which is the missing link for most teams dealing with multi-cloud sprawl.
The integration works by treating observability data as evidence instead of just telemetry. Veritas extends New Relic’s event model with identity metadata pulled from your access provider. Think of Okta users, AWS IAM roles, or SSO groups passing signed claims. Each change, deployment, or API call carries its own proof of origin. The result is forensic-grade tracing that also strengthens compliance posture without requiring a separate audit tool.
When you wire the two up, requests travel through an identity-aware proxy that inspects tokens, checks RBAC rules, and adds contextual tags before ingestion. Analysts can filter “who triggered this alert” as easily as “which container spiked CPU.” The logic is simple but powerful: trust every metric only if you can trust who generated it.
A few best practices help keep things tight:
- Rotate service credentials on a fixed schedule and store them using an external secret manager.
- Map user groups directly to Veritas scopes instead of duplicating roles.
- Log denied access attempts in the same pipeline as successful requests. Auditors love that symmetry.
Key benefits:
- Cleaner attribution for each alert or deployment event.
- Instant traceability across clouds and environments.
- Reduced mean time to innocence when investigating outages.
- Built-in compliance signals suited for SOC 2 or ISO audits.
- Shorter feedback loops between DevOps, security, and compliance teams.
For developers, this integration removes friction. You keep using standard CI/CD steps, but identity gets logged end to end. That means fewer back-and-forth messages about permissions and ownership. Developer velocity improves because everyone can see why something happened, not just what happened.
Platforms like hoop.dev take this a step further. They turn identity-aware access policies into guardrails that enforce least privilege automatically, then feed those verified contexts into tools like New Relic Veritas. The effect is observability you can actually trust without adding manual approvals.
How do I connect New Relic and Veritas?
Use your identity provider’s OIDC or SAML app to issue trust tokens recognized by Veritas. Add those claims to New Relic’s telemetry ingest pipeline. No custom code needed, just proper mapping and verification.
As AI copilots start analyzing operational data, identity-verified logs prevent poisoned context or hallucinated ownership claims. The cleaner the metadata, the safer your automation.
The takeaway: metrics tell you what’s happening; Veritas tells you who stands behind each line of data. Together, they turn observability into accountability.
See an Environment Agnostic Identity-Aware Proxy in action with hoop.dev. Deploy it, connect your identity provider, and watch it protect your endpoints everywhere—live in minutes.