Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit e893351

Browse files
committedFeb 5, 2024
Add more information about loki
1 parent 9b445cf commit e893351

File tree

2 files changed

+11
-1
lines changed

2 files changed

+11
-1
lines changed
 

‎docs/assets/grafana-loki-poster.png

1.62 MB
Loading

‎docs/observability/logs/README.md

+11-1
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ Log collection is automatically configured for persistent storage, but can be ch
4848

4949
The most recent log will always be available in nais console and using the `kubectl logs` command.
5050

51-
#### Log destinations
51+
### Log destinations
5252

5353
| Destination | ID | Description | Availability |
5454
| :-------------------------- | :------------ | :--------------------------------- | :----------- |
@@ -59,6 +59,8 @@ The most recent log will always be available in nais console and using the `kube
5959

6060
## Grafana Loki
6161

62+
![Screen shot of Grafana Loki user interface](../../assets/grafana-loki-poster.png)
63+
6264
Grafana Loki is a log aggregation system inspired by Prometheus and integrated with Grafana. It is designed to be cost effective and easy to operate, as it does not index the contents of the logs, but rather a set of predefined labels for each log stream.
6365

6466
Grafana Loki is designed to be used in conjunction with metrics and tracing to provide a complete picture of an application's performance. Without the other two, it can be perceived as more cumbersome to use than a traditional logging system.
@@ -76,6 +78,14 @@ spec:
7678
- id: loki
7779
```
7880
81+
### Working with Loki
82+
83+
Grafana Loki is integrated directly with Grafana, and you can access your logs either by adding a Logs Panel to your dashboard or by clicking on the "Explore" link on the left-hand side of the Grafana UI and selecting one of the Loki data sources (one for each environment).
84+
85+
Grafana Loki has a query language called [LogQL](https://grafana.com/docs/loki/latest/logql/) that you can use to search for logs. LogQL is a simplified version of PromQL, and you can use LogQL to search for logs by message, by field, or by a combination of both.
86+
87+
The main difference between LogQL and PromQL is the use of the pipe `|` operator. The pipe operator is used to chain together multiple LogQL expressions. This allows you to filter, aggregate, and transform logs in a single query.
88+
7989
## Elastic Kibana
8090

8191
Elasticsearch is a

0 commit comments

Comments
 (0)
Please sign in to comment.