"The new architecture replaces the replication-at-ingestion strategy with Kafka as the durability layer. Logs land in Kafka once, ingesters consume from the queue, and the effective replication factor drops to one."
"Our internal metrics show that in reality, we end up storing on average 2.3x, for every log line that we ingest, we store it 2.3 times."
"Combined with a redesigned query engine that distributes work across partitions and executes in parallel, Grafana claims up to 20x less data scanned and 10x faster performance on aggregated queries."
Grafana 13 was announced at GrafanaCON 2026, featuring a new Loki architecture that utilizes Kafka for log ingestion. This change reduces data duplication and improves performance. The previous architecture relied on replication, leading to an average of 2.3 times storage for each log line due to deduplication issues. The new design allows logs to land in Kafka once, with ingesters consuming from the queue, resulting in a significant reduction in data scanned and faster query performance. However, this introduces more dependencies compared to the original design.
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]