For Microservices
When a request touches 8 services before failing, you need one place to see what happened. LogFlow gives you trace correlation, service mapping, and cross-service search — without deploying an agent per container.
Common problems, solved
Trace correlation links logs across services by trace_id. Click once to see the full request timeline with relative timestamps.
Trace correlation docs →Service map shows connections, error rates, and latency (p50/p95/p99) per service. Built from real log data, not YAML.
Service map docs →Deployment markers overlay on charts. See exactly which deploy correlates with the spike, across all services.
Setup deploy markers →Error grouping fingerprints similar errors into Issues. One alert, not six hundred. Resolve or mute noise.
Error grouping docs →How it works
npm install @getlogflow/js — or use the HTTP API from any language. One SDK per service, no sidecar containers.
SDK docs →Add a trace_id to your logs (or use OpenTelemetry). LogFlow links them into a timeline view across services.
OpenTelemetry setup →Service map, trace correlation, error grouping, anomaly detection — all from your log data, no extra agents.
Service map docs →Free tier with 1 GB/month. Add the SDK to one service, see results in seconds.