Tink vs cAdvisor
cAdvisor is Google's container metrics binary: per-container CPU, memory, and filesystem gauges for Prometheus. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.
cAdvisor exposes container /metrics. Tink answers “why is this VPS sick?”
Accidental sysadmins land on cAdvisor because every Docker + Prometheus diagram starts with a container scrape. Then the disk fills, nginx dies, and Grafana is quiet — nothing scraped, 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 cAdvisor if you already operate Prometheus and need container gauges. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | cAdvisor |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — cadvisor binary or Docker, :8080, prometheus.yml scrape job, dashboards, and Alertmanager |
| What you get | Working monitoring, diagnosis, and approved fixes | A container scrape target. 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 rules |
| Hidden costs | None — fully managed | cgroup paths, Docker socket access, high-cardinality container labels, and a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Per-container CPU, memory, and fs gauges. cAdvisor does not watch host nginx or a quiet cert unless you added another exporter |
| Configuration | None after install — heuristics and AI | Listen address, Docker/cgroup flags, scrape intervals, relabeling, and which PromQL actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You graph container_memory_usage_bytes in Grafana, then SSH in to change the box |
| Fix execution | Proposes and executes approved commands with an audit trail | Export only — cAdvisor cannot restart nginx or free disk |
| Alerting | Built-in across 8 channels | Not a cAdvisor job — Prometheus rules and Alertmanager have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not an exporter job — a container filesystem collector 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 cAdvisor dies — unless you built an up{job="cadvisor"} deadman check |
| Public status page | Shareable URL with 90-day history | None — cAdvisor has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a container scrape target 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 :8080/metrics and Grafana. No mechanic you text when disk filled |
| Learning curve | None — works after install | Steep — cgroups, container labels, 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 container scrapes, not a sick-VPS mechanic |
When cAdvisor is the right choice
Keep cAdvisor when you already want that exact job:
- Prometheus container scrapes — you need container_cpu_usage_seconds_total in PromQL, not a mechanic.
- Per-container gauges — cgroup CPU, memory, and fs stats matter more than host nginx, certs, and SSH on a quiet VPS.
- An existing Prometheus + Grafana stack — cAdvisor already ships, dashboards already graph, and someone owns Alertmanager.
- Hosts that only export — you already run cadvisor as a container, not a sick-box SSH loop.
The real cost of “just run cAdvisor”
A container exporter is in every Docker + Prometheus diagram. A working ops loop for five Linux boxes is not:
- An exported container metric still means you SSH in and change the box by hand
- Host disk, nginx, certs, and SSH brute-force never appear unless you scraped those signals and Alertmanager paged
- cgroup paths, Docker socket access, and PromQL cardinality punish the hours you spend debugging targets
- A single VPS with a dead cAdvisor still needs a mechanic, not another scrape job
For a 5-server team, Tink Mechanic at $45/month is cheaper than cAdvisor plus the engineer who keeps Prometheus scrape alive, and every scan includes a diagnosis a quiet /metrics endpoint will not type.
No prometheus.yml homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Node Exporter · Tink vs Prometheus · Tink vs Telegraf