mirror of
https://github.com/KevinMidboe/mktxp-no-cli.git
synced 2025-10-29 17:50:23 +00:00
Update README.md
This commit is contained in:
committed by
GitHub
parent
436f4f5441
commit
540cf178fe
10
README.md
10
README.md
@@ -369,7 +369,7 @@ remote_dhcp_entry = None # An MKTXP entry for remote DHCP info resolution
|
||||
`MKTXP entry` in this context can be any other mktxp.conf entry, and for the sole purpose of providing DHCP info it does not even need to be enabled.
|
||||
|
||||
### Connections stats
|
||||
With so many smart devices everywhere, one can only wonder where do they go to and what they actually do with all the information from your network environment. MKTXP let's you track that with a single option, available both from [mktxp dashboard](https://grafana.com/grafana/dashboards/13679-mikrotik-mktxp-exporter/) and the command line:
|
||||
With many connected devices everywhere, one can only wonder where do they go to and what they actually do with all the information from your network environment. MKTXP let's you track those with a single option, available both from [mktxp dashboard](https://grafana.com/grafana/dashboards/13679-mikrotik-mktxp-exporter/) and the command line:
|
||||
|
||||
```
|
||||
connection_stats = False # Open IP connections metrics
|
||||
@@ -378,7 +378,7 @@ Setting this to `True` obviously enables the feature and allows to see something
|
||||
|
||||
<img width="2346" alt="conns" src="https://user-images.githubusercontent.com/5028474/217042107-bffa0a81-a6a0-4474-87d4-1597cdd80735.png">
|
||||
|
||||
Hey, what is this simple Temp&Humidity sensor has to do with a bunch of open network connections? 12, really?
|
||||
Hey, what is this Temp&Humidity sensor has to do with a bunch of open network connections? 12, really?
|
||||
Let's go check on that in the dashboard, or just get the info right from the commandline:
|
||||
|
||||
```
|
||||
@@ -389,17 +389,19 @@ Let's go check on that in the dashboard, or just get the info right from the com
|
||||
| T&H Cat's Room | 10.20.10.149 | 12 | 3.124.97.151:32100(udp), 13.38.179.104:32100(udp), |
|
||||
| | | | 54.254.90.185:32100(udp)
|
||||
```
|
||||
*A quick `whois` check shows all of the external IP relate to AWS, so perhaps OK for now... but we can now remain vigilant, anyway :)*
|
||||
*A quick `whois` check shows all of the external IPs relate to AWS, so perhaps it's legit... but let's remain vigilant, anyway :)*
|
||||
|
||||
|
||||
### Parallel routers fetch
|
||||
|
||||
Concurrent exports across multiple devices can considerably speed up things for slow network connections.
|
||||
```
|
||||
fetch_routers_in_parallel = False # Set to True if you want to fetch multiple routers parallel
|
||||
max_worker_threads = 5 # Max number of worker threads that can fetch routers (parallel fetch only)
|
||||
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)
|
||||
```
|
||||
To keeps things within reliable boundaries, the last two parameters allows for controlling both individual and overall scrape durations
|
||||
|
||||
|
||||
### mktxp port
|
||||
port = 49090
|
||||
|
||||
Reference in New Issue
Block a user