Add your base64 encoded password to the file mikrotik-exporter-secret.yml and run the following command: $ kubectl apply -f kubernetes-homelab/mikrotik-exporter/mikrotik-exporter-secret.yml Create a NamespaceĬreate a monitoring namespace: $ kubectl create ns monitoringĬreate a Kubernetes secret to store your Mikrotik password for the prometheus API user. Note that this homelab project is under development, therefore please refer to GitHub for any source code changes.
#Mikrotik api install#
Clone the following repository: $ git clone Install and Configure mikrotik-exporter: Step by Step user add name=prometheus group=prometheus password=changemeĬonfiguration files used in this article are hosted on GitHub. user group add name=prometheus policy=api,readĬreate a prometheus user to access the API. Configure Mikrotik RouterĮnable API service from our homelab LAN: /ip service set api address=10.11.1.0/24Ĭreate a prometheus group on the router that has API and read-only access. We are using our Kubernetes homelab to deploy mikrotik-exporter.
The latter one is an absolute beast considering its £110 (~150$) price tag. I currently use RB951G-2HnD (upgraded my old RB751G-2HnD) and RB2011UiAS-2HnD-IN. In my honest opinion, the best thing you can do with your ISP-provided router is to recycle it. I’ve been using Mikrotik for many years, and it’s done the job really well.
We are going to deploy mikrotik-exporter to visualise Prometheus monitoring data for Mikrotik.