docs: streamline formatting and proofreading
This commit is contained in:
committed by
Stefan Rotsch
parent
2c541dfbea
commit
94ac286c34
@@ -1,15 +1,13 @@
|
||||
---
|
||||
title: "Loki"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
featured: true
|
||||
tags: [ devops ]
|
||||
title: "Loki"
|
||||
ring: adopt
|
||||
quadrant: platforms-and-aoe-services
|
||||
tags: [ devops ]
|
||||
---
|
||||
|
||||
After very good experiences so far, we replaced our ELK stacks with Loki mainly for the following reasons:
|
||||
After having very positive experiences, we decided to replace our ELK stacks with Loki, primarily for the following reasons:
|
||||
|
||||
* Loki is significantly cheaper than the storage requirements of Elasticsearch used in the ELK stack.
|
||||
* The PromQL-like query language that is familiar to users of Prometheus, makes it easier for DevOps and SRE teams who
|
||||
are already using Prometheus for monitoring to work with logs.
|
||||
* Loki's native integration with kubernetes simplifies the setup and configuration process.
|
||||
* Loki typically requires less maintenance and overhead compared to ELK.
|
||||
- Loki is significantly more cost-effective than the storage requirements of Elasticsearch used in the ELK stack.
|
||||
- The PromQL-like query language, familiar to users of Prometheus, makes it easier for DevOps and SRE teams who already use Prometheus for monitoring to work with logs.
|
||||
- Loki's native integration with Kubernetes simplifies the setup and configuration process.
|
||||
- Loki typically requires less maintenance and overhead compared to ELK.
|
||||
|
||||
Reference in New Issue
Block a user