docs: fix internal links
This commit is contained in:
committed by
Stefan Rotsch
parent
014cc8d360
commit
84d5939770
@@ -5,7 +5,7 @@ quadrant: tools
|
||||
tags: [devops]
|
||||
---
|
||||
|
||||
Archiving indexed log data with a system like [Elasticsearch](../platforms-and-aoe-services/elasticsearch.html) can be expensive, and archiving it as simple text files makes it hard to query. [Loki](https://grafana.com/oss/loki/) solves this issue by adding a reference database based on [Kubernetes](../platforms-and-aoe-services/kubernetes.html) labels to each log line, similar to [Prometheus](../platforms-and-aoe-services/prometheus.html), but storing the log data inside a simple blob storage like AWS S3. This allows the user to query the data by predefined labels and keeps the costs for indexing low.
|
||||
Archiving indexed log data with a system like [Elasticsearch](/platforms-and-aoe-services/elasticsearch/) can be expensive, and archiving it as simple text files makes it hard to query. [Loki](https://grafana.com/oss/loki/) solves this issue by adding a reference database based on [Kubernetes](/platforms-and-aoe-services/kubernetes/) labels to each log line, similar to [Prometheus](/platforms-and-aoe-services/prometheus/), but storing the log data inside a simple blob storage like AWS S3. This allows the user to query the data by predefined labels and keeps the costs for indexing low.
|
||||
|
||||
Another benefit is that Loki does not have an endpoint for mutating log data, making the data immutable from a potentially compromised system.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user