Your logs can leave. The BVNs in them don't.
Application logs are full of account numbers, and they ship abroad all day. The log processor sits between your apps and your log vendor and tokenizes what it finds on the way through.
A single debug line can send thousands of customer identifiers to a vendor outside Nigeria, and nobody on the team decided that it should.
Change one endpoint
Point your OpenTelemetry Collector, Fluent Bit or Vector output at the processor.
Watch first
Run in Watch only to see what would be caught, with your logs unchanged.
Turn on protection
Identifiers become tokens. Everything else reaches your vendor as it was.
OpenTelemetry Collector
exporters:
otlphttp/onshore:
endpoint: https://logs.onshore.ng/otlp/${env:ONSHORE_PIPELINE}
headers:
X-RV-Pipeline-Key: ${env:ONSHORE_PIPELINE_KEY}
service:
pipelines:
logs:
exporters: [otlphttp/onshore]Three front-ends, one engine
OpenTelemetry, Fluent Bit and Vector all use the same detection rules.
No code changes
Your application keeps logging as it does today.
Debugging still works
Deterministic tokens mean you can still follow one customer through your logs.
Works with OTLP
HTTP and gRPC for logs, using your existing pipeline.
Traces and metrics too
OTLP traces and metrics can pass through the same pipeline.
A key per pipeline
Each pipeline has its own ingest key, and a wrong key is refused.
Start with one leak.
Tell us which flow worries you most. We'll show you what it would take to keep it onshore.