elasticsearch_exporter is Prometheus's usual Elasticsearch scrape: a :9114 /metrics endpoint of cluster health and index gauges. 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 elasticsearch_exporter because every ELK + Prometheus diagram starts with a cluster-health 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 elasticsearch_exporter if you already operate Prometheus and need Elasticsearch gauges. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | Elasticsearch Exporter |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — exporter user, ES_URI, --es.uri, :9114, prometheus.yml scrape job, dashboards, and Alertmanager |
| What you get | Working monitoring, diagnosis, and approved fixes | An Elasticsearch scrape target. Host disk, nginx, Postgres, 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 | A cluster credential, --es.all / --es.indices cardinality, and a second tool to tell you the box is sick |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | elasticsearch_cluster_health_* and elasticsearch_indices_* gauges. elasticsearch_exporter does not watch host disk or a quiet cert unless you added another exporter |
| Configuration | None after install — heuristics and AI | ES_URI, --es.uri, --es.all, scrape intervals, and which PromQL actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You graph elasticsearch_cluster_health_status in Grafana, then SSH in to change the box |
| Fix execution | Proposes and executes approved commands with an audit trail | Export only — elasticsearch_exporter cannot restart Elasticsearch or free disk |
| Alerting | Built-in across 8 channels | Not an Elasticsearch Exporter 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 cluster-health scrape 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 elasticsearch_exporter dies — unless you built an up{job="elasticsearch"} deadman check |
| Public status page | Shareable URL with 90-day history | None — elasticsearch_exporter has no customer-facing status page |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — an Elasticsearch 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 :9114/metrics and Grafana. No mechanic you text when heap filled and the cluster flipped yellow |
| Learning curve | None — works after install | Steep — ES_URI, index collectors, 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 Elasticsearch scrapes, not a sick-VPS mechanic |
Keep elasticsearch_exporter when you already want that exact job:
A search-cluster exporter is in every ELK + Prometheus diagram. A working ops loop for five Linux boxes is not:
For a 5-server team, Tink Mechanic at $45/month is cheaper than elasticsearch_exporter 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 Elastic · Tink vs Prometheus · Tink vs Node Exporter