Tink vs Postfix Exporter

postfix_exporter is Prometheus's usual Postfix scrape: a :9154 /metrics endpoint of postfix_up and showq gauges. That is not a mechanic. Tink installs in one command, watches the Linux server, explains what is wrong, and helps you fix it.

postfix_exporter exposes postfix_* gauges. Tink answers “why is this VPS sick?”

Accidental sysadmins land on postfix_exporter because every mail + Prometheus diagram starts with a showq scrape. Then the disk fills, nginx dies, and Grafana is quiet — nothing scraped, so nothing fired. A deferred queue eating /var/spool is a Tink warning; it is not an exporter job.

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 postfix_exporter if you already operate Prometheus and need Postfix gauges. Use Tink if you run Linux servers and want a mechanic.

FeatureTinkPostfix Exporter
Setup time30 seconds (one curl | sh command)Hours — binary, showq socket, :9154, prometheus.yml scrape job, dashboards, and Alertmanager
What you getWorking monitoring, diagnosis, and approved fixesA Postfix scrape target. Host disk, nginx, Postgres, and certs stay your problem until PromQL fires and you SSH in
PricingFree (Scout) / $9 / $29 per machine per monthFree software (Apache 2.0). You still pay for Prometheus, Grafana, Alertmanager, and the engineer who writes the rules
Hidden costsNone — fully managedA showq unix socket, queue cardinality, an open 25/465, and a second tool to tell you the box is sick
Monitoring approachAgent on the server — CPU, disk, services, logs, certs, portspostfix_up and postfix_showq_message_size_bytes gauges. postfix_exporter does not watch host disk or a quiet cert unless you added another exporter
ConfigurationNone after install — heuristics and AI--postfix.showq-path, scrape intervals, and which PromQL actually pages you
Plain-English diagnosisYes — AI explains root cause, impact, and fixYou graph postfix_showq_message_size_bytes in Grafana, then SSH in to change the box
Fix executionProposes and executes approved commands with an audit trailExport only — postfix_exporter cannot restart postfix, flush deferred, or free disk
AlertingBuilt-in across 8 channelsNot a Postfix Exporter job — Prometheus rules and Alertmanager have to fire
Predictive alertsYes — disk fills in ~6 days, memory and CPU trendsNot an exporter job — a showq scrape does not forecast a quiet volume
SSH brute-force detectionBuilt-in — parses auth.log every scanOnly if you ship auth.log elsewhere, parse it, write a query, and wire an alert downstream
Machine offline detectionAgent presence monitoring with multi-channel alertsSilence if postfix_exporter dies — unless you built an up{job="postfix"} deadman check
Public status pageShareable URL with 90-day historyNone — postfix_exporter has no customer-facing status page
Weekly fleet digestAutomated Monday digest + daily brief when issues are openNone — a Postfix scrape target is not a plain-English fleet narrative
On-call trackingBuilt-in /oncall command + incident acknowledgmentNot included — wire Alertmanager into PagerDuty or another incident tool
Conversation interfaceTelegram, WhatsApp, web dashboard, CLIcurl :9154/metrics and Grafana. No mechanic you text when deferred filled the spool and 25 was open to the world
Learning curveNone — works after installSteep — showq socket, PromQL, scrape configs, and which rule actually pages
Best forFreelancers, small teams, accidental sysadmins (1-50 Linux servers)Teams that already run Prometheus and need Postfix scrapes, not a sick-VPS mechanic

When Postfix Exporter is the right choice

Keep postfix_exporter when you already want that exact job:

  • Prometheus Postfix scrapes — you need postfix_showq_message_size_bytes in PromQL, not a mechanic.
  • Per-queue and SMTP gauges — deferred length, bounce codes, and showq sizes matter more than host nginx, certs, and SSH on a quiet VPS.
  • An existing Prometheus + Grafana stack — postfix_exporter already ships, dashboards already graph, and someone owns Alertmanager.
  • Hosts that only export — you already run postfix_exporter next to Postfix, not a sick-box SSH loop.

The real cost of “just run postfix_exporter”

A mail exporter is in every Postfix + Prometheus diagram. A working ops loop for five Linux boxes is not:

  • An exported deferred-queue 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
  • A filling /var/spool/postfix is a Tink disk warning on every scan — postfix_exporter will keep scraping it
  • A single VPS with a dead postfix_exporter still needs a mechanic, not another scrape job

For a 5-server team, Tink Mechanic at $45/month is cheaper than postfix_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 Mechanic

Also compare: Tink vs Node Exporter · Tink vs Prometheus · Tink vs Apache Exporter