Tink vs Alertmanager
Alertmanager is Prometheus's alert router: it deduplicates, groups, inhibits, and sends what Prometheus already fired to Slack or PagerDuty. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
Alertmanager routes the page. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Alertmanager because every Prometheus diagram ends with a receiver. Then the volume fills, nginx dies, and Slack is quiet — no rule matched, so nothing grouped. A filling /var is a Tink warning; it is not an Alertmanager job until Prometheus already knew.
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 Alertmanager if you already operate Prometheus and need routing. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Alertmanager |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — Prometheus, alerting rules, alertmanager.yml routes, receivers, silences, and HA gossip if you want it up |
| What you get | Working monitoring, diagnosis, and approved fixes | Dedup, grouping, inhibition, and a route to Slack. The box is still yours to diagnose and SSH |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Free software (Apache 2.0). You still pay for Prometheus, exporters, Grafana, and the engineer who owns the routing tree |
| Hidden costs | None — fully managed | alertmanager.yml, inhibition matches, silence UX, cluster peers on :9093, and a second tool that actually watches the server |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | None — Alertmanager never scrapes. It only handles alerts Prometheus already decided to fire |
| Configuration | None after install — heuristics and AI | route trees, matchers, group_by, repeat_interval, receivers, and which silence actually mutes the page |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | No — Alertmanager templates the labels Prometheus sent. You still SSH in to learn why |
| Fix execution | Proposes and executes approved commands with an audit trail | Routing only — Alertmanager cannot free disk, restart nginx, or rotate a cert |
| Alerting | Built-in across 8 channels | Email, Slack, PagerDuty, Opsgenie, webhooks — after Prometheus fired and the route matched |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Only if you already wrote a PromQL forecast rule. Alertmanager does not predict |
| SSH brute-force detection | Built-in — parses auth.log every scan | Only if an exporter shipped auth.log, a rule fired, and the route reached you |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if Prometheus itself is down — unless you built a deadman switch into the route tree |
| Public status page | Shareable URL with 90-day history | None — Alertmanager has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a grouped page is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire a receiver into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | amtool, the :9093 UI, and Slack. No mechanic you text when /var filled and nothing grouped |
| Learning curve | None — works after install | Steep — PromQL rules, route trees, inhibition, silences, and HA clustering |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Prometheus and need alert routing, not a sick-VPS mechanic |
When Alertmanager is the right choice
Keep Alertmanager when you already want that exact job:
- Prometheus alert routing — you need grouping, inhibition, and silences, not a mechanic.
- Multi-receiver fan-out — Slack plus PagerDuty plus email from one route tree matters more than host nginx, certs, and SSH on a quiet VPS.
- An existing Prometheus + Grafana stack — rules already fire, Alertmanager already clusters, and someone owns the config.
- Hosts that only page — you already run exporters and PromQL, not a sick-box SSH loop.
The real cost of “just run Alertmanager”
Alertmanager is in every Prometheus diagram. A working ops loop for five Linux boxes is not:
- A grouped Slack page still means you SSH in and change the box by hand
- Host fill, nginx, certs, and SSH brute-force never appear unless Prometheus scraped those signals and a rule fired
- A filling /var is a Tink disk warning on every scan — Alertmanager will stay quiet until a PromQL expression exists
- A single VPS with a dead Alertmanager still needs a mechanic, not another route tree
For a 5-server team, Tink Mechanic at $45/month is cheaper than Alertmanager plus the engineer who keeps Prometheus rules and the routing tree alive, and every scan includes a diagnosis a quiet :9093 UI will not type.
No alertmanager.yml homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Prometheus · Tink vs PagerDuty · Tink vs Opsgenie