![]() # Added ?: to regex to speed up extraction # Change App name from "MikroTik 3.7" to "MikroTik App for Splunk" # Removed x/y axes in "MikroTik VPN Connections" # Added script version in "MikroTik Device List" # Removed clients with 0 bytes in "MikroTik Device Traffic" ![]() # Removed outputlookup from "MikroTik Device List" # Added DNS for interface for "MikroTik Neighbor" # Fixed transaction due to rsyslog in "MikroTik Neighbor" # Added version info in header to conform with Splunk v9.0 Turn fast track off and you may loose throughput, so its something you should consider when using this type of monitoring. Traffic monitoring does not work correctly while fast track is enabled (and its removed in v7.x of RouterOS. All data are sent from the device to the Splunk monitor (using sctipt and syslog). No ports needs to be opened (like with SNMP monitoring). Splunk can be used to monitor multiple devices. NB logging large amount of Accouning, DNS or firewall rules quickly eats up license, so I do recommend to turn off Accouning/DNS logging to start with. You can request a 10GB/day developer license here: Splunk is free to use for logging up to 500MB pr day. Using Splunk to monitor and graph various data from our MikroTik Routers is a nice and free way to help you showing what is going on in your network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |