Core concepts
Key terms and architecture of LogFlow.
Projects
A project is an isolated namespace for logs. Each project has its own API key, retention policy, and settings. Typical usage: one project per application or environment (e.g. my-app-production, my-app-staging).
Log entry
Every log has a level, message, timestamp, and optional fields like service, host, traceId, and attributes. Logs are immutable once ingested.
Trace ID
A traceId links logs across multiple services that handled the same request. Pass the same trace ID through all services in a request chain to enable trace correlation and Service Map connections.
Retention
Logs are automatically deleted after the retention period for your plan (3 days on Free, up to 90 days on Pro). Retention is enforced per project.
Ingestion rules
Rules applied at write time to drop or sample logs before they're stored. Useful for reducing volume and cost from high-frequency, low-value logs like health checks.