Avoid dropped logs due to out-of-order timestamps with a new Loki feature | Grafana Labs
grafana.com · 534 words · saved by 1 readers
We’ll allow out-of-order writes in the next Loki release, but you can try out the functionality now on Grafana Cloud
This blog post was written with Senior Technical Writer Karen Miller. Dropped log lines due to out-of-order timestamps can be a thing of the past! Allowing out-of-order writes has been one of the most-requested features for Loki, and we’re happy to announce that in the upcoming v2.4 release, the requirement to have log lines arrive in order by timestamp will be lifted. Simple configuration will allow out-of-order writes for Loki v2.4. If you’re using Grafana Cloud, our fully managed platform integrating metrics, logs, traces, and dashboards, out-of-order writes are already accepted. The…
saved by
related reading
- ObservabilityCON 2022: A guide to new OSS projects, LGTM stack updates, and more from Grafana Labsgrafana.com
- Grafana Labs at KubeCon: What is the Future of Observability?grafana.com
- Grafana OSS | Leading observability tool for visualizations & dashboardsgrafana.com
- Announcing Grafana Phlare, the open source database for continuous profiling at massive scalegrafana.com
- Introducing Husky, Datadog’s third-generation event store | Datadogdatadoghq.com
- Time, Clocks, and the Ordering of Events in a Distributed Systemlamport.azurewebsites.net
- V2.6 | Grafana Loki documentationgrafana.com
- evlog — Digging through logs is not observability. It's hope.evlog.dev
- Logging, Tracing, Monitoring, et al.alexandruburlacu.github.io
- Lamport timestamp - Wikipediaen.wikipedia.org
- From monolith to Lakebase to LTAP: rethinking the database from storage up | Databricks Blogdatabricks.com
- Durable Execution Solutionstemporal.io