mikrotik-exporter

KO | EN

gitlite — search

#ai #go #android #machine-learning #rust #deep-learning #linux #docker #nodejs #windows #awesome #vue #ios #mcp

mikrotik-exporter

(★ 613)

prometheus mikrotik device(s) exporter

파일 탐색기

최종 버전 다운로드 (.zip)

- - ci.yml
- bgp_collector.go
- capsman_collector.go
- cloud_collector.go
- cloud_collector_test.go
- collector.go
- collector_context.go
- conntrack_collector.go
- dhcp_collector.go
- dhcp_lease_collector.go
- dhcpv6_collector.go
- firmware_collector.go
- health_collector.go
- helper.go
- helper_test.go
- interface_collector.go
- ipsec_collector.go
- lte_collector.go
- monitor_collector.go
- netwatch_collector.go
- optics_collector.go
- poe_collector.go
- pool_collector.go
- resource_collector.go
- resource_collector_test.go
- routeros_collector.go
- routes_collector.go
- w60g_collector.go
- wlanif_collector.go
- wlansta_collector.go
- config.go
- config.test.yml
- config_test.go
- - .env
  - docker-compose.yml
- build-armhf.sh
- build.sh
- start.sh
.gitignore
.ko.yaml
AGENTS.md
Dockerfile
go.mod
go.sum
LICENSE
main.go
MAINTAINERS.md
Makefile
README.md
VERSION

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![Docker Pulls](https://img.shields.io/docker/pulls/nshttpd/mikrotik-exporter.svg)](https://hub.docker.com/r/nshttpd/mikrotik-exporter/)

## 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`

If `lte` is enabled it requires also the `test` policy.

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

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.

User and password flags can be set with the `MIKROTIK_USER` and `MIKROTIK_PASSWORD` environment variables, respectively.

```
MIKROTIK_USER=prometheus
MIKROTIK_PASSWORD=changeme
./mikrotik-exporter -address 10.10.0.1 -device my_router
```

#### Config File

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

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

###### example config
```yaml
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
    wifiwave2: true
  - name: routers_srv_dns
    srv:
      record: _mikrotik._udp.example.com
    user: prometheus
    password: password_to_all_dns_routers
  - name: routers_srv_custom_dns
    srv:
      record: _mikrotik2._udp.example.com
      dns:
        address: 1.1.1.1
        port: 53
    user: prometheus
    password: password_to_all_dns_routers

features:
  bgp: true
  dhcp: true
  dhcpv6: true
  dhcpl: true
  routes: true
  pools: true
  optics: true
  wlanif: true
  wlansta: true
```

If you add a devices with the `srv` parameter instead of `address` the exporter will perform a DNS query
to obtain the SRV record and discover the devices dynamically. Also, you can specify a DNS server to use
on the query.

Use the option `wifiwave2: true` for devices that have the `wifiwave2` package,
which replaces the `wireless` implementation, installed. This is necessary as `wifiwave2` has a slightly
different API and exposes a slightly smaller set of attributes (for example, no signal-to-noise, etc.)

###### 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
```

mikrotik-exporter

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

mikrotik-exporter

파일 탐색기

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README