WHAT IS FEDERATED LOGS ?
Stop choosing between data residency and visibility
HOW IT WORKS
Three steps to data residency
- Deploy pipeline control gateway into your Kubernetes cluster from a prebuilt template, plus cloud resources to store and manage Federated Logs data
- The gateway’s pre-built processors parse, enrich, and obfuscate logs data then route them to your object storage (e.g. Amazon S3) in efficient formats
- New Relic manages a query engine that runs in the same region and returns results to the New Relic UI
ACCELERATE MTTR
Logs in context, wherever logs reside
- Pivot from a trace or application errors to the related logs without context switching across tools
- Query federated logs with the same NRQL, UI, and dashboards you use for the rest of your telemetry stored in NRDB
- Get pre-built processors for your logs in context, no more manual stitching
REDUCE OPERATIONAL TOIL
One pipeline instead of a second logging stack
- Retire the parallel logging stack maintained purely to satisfy residency obligations
- Bring back the logs you’ve been leaving out, and query them together with everything else
- Parse, enrich, and obfuscate logs in one gateway before they land in your storage
DATA RESIDENCY BY DESIGN
Global platform, regional data
- Log data is processed and stored at rest in your own cloud account and region
- Query requests are routed to your region, and query results that transit to New Relic are encrypted and not stored outside your region
- Standardize observability globally while log data stays and is queried in its region of origin