Skip to content

Latest commit

 

History

598 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

MKTXP

License Language Platform Diagnostics GitOps Prometheus Docker Pulls

MKTXP is an extensible toolkit for MikroTik RouterOS network engineering. It provides interactive terminal diagnostics, deterministic GitOps configuration management, and a Prometheus metrics exporter within a single command-line tool.


Choose Your Workflow

I need to … Start with Full Guide
Troubleshoot a router now mktxp diag … CLI Diagnostics Guide
Clean up / version RouterOS configs mktxp rsc … GitOps RSC Guide
Monitor routers continuously mktxp export Prometheus Exporter Guide

Install

Standalone CLI & Exporter

# Recommended for local CLI usage
❯ pipx install mktxp

# Or via standard pip
❯ pip install mktxp

# Via Homebrew
❯ brew install mktxp

# Via Docker
❯ docker pull ghcr.io/akpw/mktxp:latest

Requirements: Python >= 3.9. Supported on Linux, macOS, and FreeBSD.

Ready-to-Run Monitoring & Logging Stack

If you need a turnkey environment without manually wiring services, MKTXP Stack is an out-of-the-box Docker Compose deployment that packages MKTXP alongside Prometheus / Grafana stack with pre-configured dashboards, and adds centralized MikroTik syslog processing via Loki and Promtail.


Quick Start: GitOps Configuration (mktxp rsc)

For local .rsc files, mktxp rsc works with zero configuration or router setup required:

# Deterministic formatting: single-line commands, standardized headers, and clean Git diffs
❯ mktxp rsc format -i backup.rsc -o clean_backup.rsc

# Modular domain splitting: break a monolithic export into numbered component files and extracted scripts
❯ mktxp rsc split -i backup.rsc -o ./config-repo/ --extract-scripts

📖 For AST architecture, custom domain handlers, live backups over SSH, and CI/CD automation, see the GitOps RSC Guide.


Connect to a Router

Both Live Diagnostics and the Prometheus Exporter connect to your routers via the standard RouterOS API.

MKTXP uses two configuration files:

  • mktxp.conf: Router connection profiles, credentials, custom labels, and metrics switches. Edit with mktxp edit.
  • _mktxp.conf: Daemon listen sockets, timeouts, parallel scraping, GitOps rules, and CLI diagnostic thresholds. Edit with mktxp edit -i.

Files are resolved automatically from ~/.config/mktxp/ (XDG standard) or /etc/mktxp/ (system/Docker). Check active paths anytime with mktxp show -cfg.

1. Minimal Configuration (mktxp.conf)

Add your router entry to mktxp.conf:

[My-Router]
    hostname = 192.168.88.1
    username = mktxp_user
    password = secret_password

(For Docker, simply mount your config directory: -v "$(pwd)/mktxp-config:/etc/mktxp")

2. Router User Setup

Create a dedicated monitoring user on your MikroTik router:

/user group add name=mktxp_group policy=api,read
/user add name=mktxp_user group=mktxp_group password=secret_password

(Note: For LTE metrics on RouterOS v6, the user also needs the test permission policy.)

📖 For complete parameter references, [default] section inheritance, custom labels, parallel fetching, and diagnostic tuning, see the Configuration Guide.


Quick Start: Live Diagnostics (mktxp diag)

Run targeted, domain-specific diagnostic one-liners directly in your terminal:

# Find sticky wireless clients clinging to distant APs with poor signal or low rates
❯ mktxp diag -en My-Router -cc --low-signal --low-rate 1M

# Surface top bandwidth consumers across the network
❯ mktxp diag -en My-Router -kc --top 5

# Audit mystery DHCP devices with no hostname
❯ mktxp diag -en My-Router -dc --unidentified

# Check active dynamic firewall threat bans
❯ mktxp diag -en My-Router -al blacklist --dynamic-only

# Pinpoint degraded cables or ports negotiating down (< 100 Mbps or half-duplex)
❯ mktxp diag -en My-Router -im --degraded

Sample output:

+----------------------+--------------+-------------------+-----------+------------------+--------+---------+---------+---------+
|      dhcp_name       | dhcp_address |    mac_address    | rx_signal |    interface     |  ssid  | tx_rate | rx_rate | uptime  |
+======================+==============+===================+===========+==================+========+=========+=========+=========+
| wlan0 (Conf Printer) | 10.20.10.49  | D8:1F:12:AD:3C:55 |    -87    | AP-Breakroom-2G  | Office | 36 Mbps | 1 Mbps  | 6 hours |
| wlan0 (Boardroom Tab)| 10.20.10.97  | 10:5A:17:0C:B9:C8 |    -84    | AP-Reception-2G  | Office | 24 Mbps | 1 Mbps  |  a day  |
+----------------------+--------------+-------------------+-----------+------------------+--------+---------+---------+---------+
Matching CAPsMAN clients: 2 (Total connected: 127)

💡 Tip: Appending -h to any command (e.g. mktxp diag -kc -h) dynamically scopes help to only that command's filters.
📖 For more diagnostic domains, table schemas, and recipes, see the Diagnostics Guide.


Quick Start: Prometheus Exporter (mktxp export)

Start the exporter daemon to scrape configured routers and serve metrics to Prometheus:

❯ mktxp export
# Serving Prometheus metrics at http://localhost:49090/metrics

Add the scrape target to /etc/prometheus/prometheus.yml:

scrape_configs:
  - job_name: 'mktxp'
    static_configs:
      - targets: ['localhost:49090']

Import the official Grafana Dashboard (ID: 13679):

Traffic & Interface Wireless Clients Device Health

💡 Tip: Want centralized RouterOS logs too? MKTXP Stack is an out-of-the-box Docker Compose deployment that packages MKTXP alongside Prometheus / Grafana stack with pre-configured dashboards, and adds centralized MikroTik syslog processing via Loki and Promtail.

MKTXP Stack Centralized Logging

💡 Tip: 📖 For dynamic multi-target discovery (/probe), Docker/Kubernetes, and systemd/FreeBSD service deployment, see the Exporter Guide.


Detailed Documentation


Blogs


License & Contributing

  • Distributed under the GNU General Public License v2.
  • Local development:
    • Create a virtual environment: python3 -m venv .venv && source .venv/bin/activate
    • Install editable with test dependencies: pip install -e ".[test]"
    • Run test suite: pytest
    • Install latest development build directly: pip install git+https://github.com/akpw/mktxp

About

CLI Diagnostic, Prometheus Exporter, and GitOps Configuration for Mikrotik RouterOS devices

Resources

Stars

1.1k stars

Watchers

14 watching

Forks

Releases

Sponsor this project

Packages

Used by

Contributors

Languages