From f972e73f6540ee0693eabb5f8bb27f9ee151f834 Mon Sep 17 00:00:00 2001 From: Arseniy Kuznetsov Date: Thu, 19 Jan 2023 09:05:46 +0100 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 417c800..d997cdc 100644 --- a/README.md +++ b/README.md @@ -193,7 +193,7 @@ Connecting to router MKT-LR@10.**.*.** ```` ## MKTXP system configuration -In case you need more control on how MKTXP is run, it can be done via editing the `_mktxp.conf` file. This allows things like changing the port and other impl-related parameters, enable parallel router fetching and configurable scrapes timeouts, etc. +In case you need more control on how MKTXP is run, it can be done via editing the `_mktxp.conf` file. This allows things like changing the port 💡 and other impl-related parameters, enable parallel router fetching and configurable scrapes timeouts, etc. As before, for local installation the editing can be done directly from mktxp: ``` mktxp edit -i @@ -219,7 +219,7 @@ mktxp edit -i max_scrape_duration = 10 # Max duration of individual routers' metrics collection (parallel fetch only) total_max_scrape_duration = 30 # Max overall duration of all metrics collection (parallel fetch only) ``` - +💡 *When changing the default mktxp port for [docker-based installs](https://github.com/akpw/mktxp#docker-image-install), you'll also need to adjust your `docker run -p ...` to reflect the new port* ## Grafana dashboard Now with your RouterOS metrics being exported to Prometheus, it's easy to visualize them with this [Grafana dashboard](https://grafana.com/grafana/dashboards/13679)