prometheus mikrotik device(s) exporter
Go to file
2020-02-03 22:00:00 -05:00
.circleci switch to go modules (#58) 2019-11-16 00:05:31 -05:00
collector Fix routes collector to be compatible with latest RouterOS release (#66) 2020-02-03 21:33:02 -05:00
config added DHCPL collection to configs and collectors (#69) 2020-02-03 22:00:00 -05:00
examples/kubernetes/single-device more dev work (#1) 2017-09-16 22:38:01 -04:00
scripts fixed typo in start.sh permissions assignment (#53) 2019-10-16 12:07:35 -04:00
.gitignore #36 attempt to fix api login auth issue (#38) 2019-07-02 20:46:19 -04:00
Dockerfile use debian instead of alpine 2019-07-21 18:10:43 -04:00
Dockerfile.arm64 various issues fixing (#49) 2019-09-02 14:51:14 -04:00
Dockerfile.armhf Fix docker build to make runnable executable (#39) 2019-07-05 22:17:33 -04:00
go.mod switch to go modules (#58) 2019-11-16 00:05:31 -05:00
go.sum switch to go modules (#58) 2019-11-16 00:05:31 -05:00
LICENSE edit and tickle to build 2019-02-21 22:42:14 -05:00
main.go added DHCPL collection to configs and collectors (#69) 2020-02-03 22:00:00 -05:00
MAINTAINERS.md clean up and adding in additional files 2017-10-12 08:36:20 -04:00
Makefile switch to go modules (#58) 2019-11-16 00:05:31 -05:00
README.md Custom API port (#62) 2019-12-26 13:17:27 -05:00
VERSION switch to go modules (#58) 2019-11-16 00:05:31 -05:00

Docker Pulls

prometheus-mikrotik

tl;dr - prometheus exporter for mikrotik devices

This is still a work in progress .. consider master at the moment as a preview release.

Description

A Prometheus Exporter for Mikrotik devices. Can be configured to collect metrics from a single device or multiple devices. Single device monitoring can be configured all on the command line. Multiple devices require a configuration file. A user will be required that has read-only access to the device configuration via the API.

Currently the exporter collects metrics for interfaces and system resources. Others can be added as long as published via the API.

Mikrotik Config

Create a user on the device that has API and read-only access.

/user group add name=prometheus policy=api,read,winbox

Create the user to access the API via.

/user add name=prometheus group=prometheus password=changeme

Single Device

./mikrotik-exporter -address 10.10.0.1 -device my_router -password changeme -user prometheus

where address is the address of your router. device is the label name for the device in the metrics output to prometheus. The user and password are the ones you created for the exporter to use to access the API.

Config File

./mikrotik-exporter -config-file config.yml

where config-file is the path to a config file in YAML format.

example config
devices:
  - name: my_router
    address: 10.10.0.1
    user: prometheus
    password: changeme
  - name: my_second_router
    address: 10.10.0.2
    port: 8999
    user: prometheus2
    password: password_to_second_router

features:
  bgp: true
  dhcp: true
  dhcpv6: true
  dhcpl: true
  routes: true
  pools: true
  optics: true
example output
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether2",name="my_router"} 1.4189902583e+10
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether3",name="my_router"} 2.263768666e+09
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether4",name="my_router"} 1.6572299e+08
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether5",name="my_router"} 1.66711315e+08
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether6",name="my_router"} 1.0026481337e+10
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether7",name="my_router"} 3.18354425e+08
mikrotik_interface_tx_byte{address="10.10.0.1",interface="ether8",name="my_router"} 1.86405031e+08