Tink vs Linkerd
Linkerd is a CNCF service mesh. It also exposes golden request metrics from Rust sidecars 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.
Linkerd scrapes the mesh. Tink answers “why is this VPS sick?”
Accidental sysadmins land on Linkerd because every service-mesh roundup lists it as the lighter Istio. Then the volume fills, nginx dies, and Grafana still shows meshed success rate — no PromQL matched host fill. A filling /var is a Tink warning; it is not a Linkerd job unless the sidecar itself is the failure.
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 scraping Linkerd if you already operate Kubernetes and need mesh SLOs. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Linkerd |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — Helm control plane, proxy-injector, namespace inject annotations, and a Prometheus scrape of linkerd-proxy |
| What you get | Working monitoring, diagnosis, and approved fixes | Golden metrics for meshed pods. Host disk fill, nginx, Postgres, and certs stay your problem until PromQL fires and you SSH in |
| Pricing | Free (Scout) / $9 / $29 per machine per month | Open-source Linkerd is free. Buoyant Linkerd is extra. You still pay Kubernetes, Prometheus, Grafana, and the engineer who owns the mesh |
| Hidden costs | None — fully managed | Sidecar CPU, inject misses, identity cert rotation, and a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | request_total, success rate, and latency histograms. Linkerd does not watch host fill or a quiet cert unless you added another exporter |
| Configuration | None after install — heuristics and AI | Inject annotations, traffic splits, authorization policy, and which PromQL actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You graph linkerd_proxy_request_duration in Grafana, then SSH in to change the box |
| Fix execution | Proposes and executes approved commands with an audit trail | Metrics only — Linkerd cannot free disk, restart nginx, or rotate a host cert |
| Alerting | Built-in across 8 channels | Not a Linkerd job — Prometheus rules and Alertmanager have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a Linkerd job — a mesh scrape does not forecast a quiet volume filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — Linkerd does not read auth.log, journald, or host firewall state |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the node dies — unless you built an up{job="linkerd-proxy"} deadman check |
| Public status page | Shareable URL with 90-day history | None — Linkerd has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a sidecar 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 | linkerd viz and Grafana. No mechanic you text when /var filled and meshed RPS still looked fine |
| Learning curve | None — works after install | Steep — inject, identity, traffic splits, PromQL, and which 5xx is the app vs the proxy |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run Kubernetes and need Linkerd golden metrics, not a sick-VPS mechanic |
When Linkerd metrics are the right choice
Keep scraping Linkerd when you already want that exact job:
- Kubernetes mesh SLOs — you need success rate, RPS, and latency for meshed pods, not a mechanic.
- An existing Linkerd cluster — mTLS, inject, and traffic splits matter more than host nginx, certs, and SSH on a quiet VPS.
- An existing Prometheus + Grafana stack — linkerd-proxy already injects, metrics already scrape, and someone owns the mesh.
- Hosts that only page on Linkerd — you already run exporters and PromQL, not a sick-box SSH loop.
The real cost of “just scrape Linkerd”
Linkerd is in every lighter-than-Istio roundup. A working ops loop for five Linux boxes is not:
- A healthy meshed success rate 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 — Linkerd will stay quiet until the sidecar itself is the failure
- A single VPS with a dead node still needs a mechanic, not another mesh scrape
For a 5-server team, Tink Mechanic at $45/month is cheaper than Linkerd plus the engineer who keeps Prometheus scrapes and sidecar inject rules alive, and every scan includes a diagnosis a quiet Grafana board will not type.
No mesh homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs Envoy · Tink vs Cilium · Tink vs Prometheus