Blackbox Exporter is Prometheus's probe binary: HTTP, HTTPS, DNS, TCP, and ICMP checks that return probe_success. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
Accidental sysadmins land on Blackbox because every Prometheus uptime diagram starts with a /probe scrape. Then the disk fills, nginx dies, and Grafana is quiet — the URL still 200s, so nothing fired.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep Blackbox if you already operate Prometheus and need URL probes. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Blackbox Exporter |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — blackbox.yml modules, :9115, prometheus.yml scrape with ?target=, dashboards, and Alertmanager |
| What you get | Working monitoring, diagnosis, and approved fixes | A probe scrape. Host disk, nginx, and certs stay your problem until PromQL fires and you SSH in |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free software (Apache 2.0). You still pay for Prometheus, Grafana, Alertmanager, and the engineer who writes the modules |
| Hidden costs | None — fully managed | Module YAML, relabeling, ICMP capabilities, TLS probe flags, and a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | External HTTP/HTTPS/DNS/TCP/ICMP probes. Blackbox does not watch host memory or a quiet cert unless you added another exporter |
| Configuration | None after install — heuristics and AI | blackbox.yml modules, scrape intervals, relabel configs, and which PromQL actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You graph probe_success in Grafana, then SSH in to change the box |
| Fix execution | Proposes and executes approved commands with an audit trail | Probe only — Blackbox cannot restart nginx or free disk |
| Alerting | Built-in across 8 channels | Not a Blackbox job — Prometheus rules and Alertmanager have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a probe job — an HTTP check does not forecast a quiet volume |
| SSH brute-force detection | Built-in — parses auth.log every scan | Only if you ship auth.log elsewhere, parse it, write a query, and wire an alert downstream |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the probe host dies — unless you built an up{job="blackbox"} deadman check |
| Public status page | Shareable URL with 90-day history | None — Blackbox has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a probe scrape is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire Alertmanager into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | curl :9115/probe and Grafana. No mechanic you text when disk filled |
| Learning curve | None — works after install | Steep — modules, relabeling, PromQL, scrape configs, and which rule actually pages |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Prometheus and need URL probes, not a sick-VPS mechanic |
Keep Blackbox when you already want that exact job:
A probe exporter is in every Prometheus uptime diagram. A working ops loop for five Linux boxes is not:
For a 5-server team, Tink Mechanic at $45/month is cheaper than Blackbox plus the engineer who keeps Prometheus scrape alive, and every scan includes a diagnosis a quiet probe_success will not type.
No blackbox.yml homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Node Exporter · Tink vs Uptime Kuma · Tink vs cAdvisor