From b4064b02992ac4a2211f495ed68f41e34f380d27 Mon Sep 17 00:00:00 2001 From: Arseniy Kuznetsov Date: Thu, 5 Jan 2023 12:37:38 +0100 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4d450cd..f4d9312 100644 --- a/README.md +++ b/README.md @@ -50,7 +50,7 @@ Now give the containers some time to start up, and then point a Web browser to [ #### Mikrotik Centralized Logging configuration In addition to RouterOS devices monitoring, MKTXP-Stack provides a preconfigured [syslog-ng](https://www.syslog-ng.com/) / [promtail](https://grafana.com/docs/loki/latest/clients/promtail/) / [Loki](https://grafana.com/docs/loki/latest) stack to receieve & process logs from multiple Mikrotik RouterOS devices in a centralized location: -![](https://user-images.githubusercontent.com/5028474/198598490-3664a3db-a6ca-4312-b34a-a34fbc12a634.png) +loki To make this work, we need to configure our Mikrotik devices to send their logs to a specified log server target. Let's first configure the corresponding remote logging action (replace XX.XX.XX.XX with your docker-compose host IP address): ```