Configure Grafana Mimir to accept out-of-order sample ingestion
domain: grafana.com · 6 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
Set `out_of_order_time_window` under `limits` (or the `-ingester.out-of-order-time-window` CLI flag) to the maximum acceptable sample age, e.g. 5m or higher
Apply the setting per tenant via runtime overrides if only specific tenants need OOO ingestion
Confirm ingesters are using the write-behind log path for OOO samples until they're uploaded to long-term storage
Align query-frontend caching behavior with the OOO window (e.g. reduce cache freshness or TTL for recent, potentially-still-arriving data)
If recording rules run more frequently than the OOO window allows for late data to settle, add an evaluation delay so rules don't compute against incomplete data
Test with a known out-of-order sample source and confirm the samples are ingested rather than rejected
Known gotchas
The default `out_of_order_time_window` is 0, meaning OOO ingestion is disabled unless explicitly configured
Setting the window back to 0 stops accepting new OOO samples but does not remove previously-ingested ones
Wider OOO windows increase resource usage on ingesters and can delay compaction/upload of blocks to long-term storage
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?