You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the most powerful way to correlate application logs with traces can be performed via Grafana's Explore interface.
32
32
33
33
After setting the datasource to Loki, all the log labels become available, and can be easily filtered using [Loki's LogQL query language](https://grafana.com/docs/loki/latest/logql/).
34
34
35
-
For example after selecting the compose project, errors can be filtered with the following expression:
35
+
For example, after selecting the compose project/service under Log labels , errors can be filtered with the following expression:
@@ -44,13 +44,12 @@ which will list the redis timeout events.
44
44
45
45
Since the HotROD application can expose its metrics in Prometheus' format, these can be also used during investigation.
46
46
47
-
This example includes a dashboard, which contains a log panel, which displays the logs for the selected services in real time. These can be also filtered by a search field.
47
+
This example includes a dashboard that contains a log panelfor the selected services in real time. These can be also filtered by a search field, that provides `grep`-like features.
48
48
49
49
There are also panels to display the ratio/percentage of errors in the current timeframe.
50
50
51
51
Additionally, there are graphs for each service, visualing the rate of the requests and showing latency percentiles.
52
52
53
53
### Clean up
54
54
55
-
To stop the containers use `docker-compose -f path-to-yml-file down`
0 commit comments