Get early access
Features · Monitoring · Service Plugins
Monitoring · Service Plugins

Deep metrics,
auto-attached.

MySQL, PostgreSQL, Redis, Nginx, Apache, Docker, PHP-FPM — when the agent discovers one, the matching plugin attaches itself. No config file, no per-host setup, no exporter sidecars.

auto-attached · web-prod-04
mysql slow 0.4/s · conn 42
postgres cache hit 99.2%
redis hit ratio 94% · evict 0
nginx upstream p95 88ms
php-fpm queue 0 · workers 12
— Why this matters

Generic CPU metrics do not debug a slow query.

01

The useful signals are service-specific.

MySQL slow-query rate, Redis hit ratio, Nginx upstream timing. None of those are visible from the outside.

02

Config is as diagnostic as runtime.

A buffer pool sized for the old server explains more than a graph. Both are collected.

03

Override files are where the surprise lives.

A setting you never changed can still be wrong because conf.d or an ALTER SYSTEM changed it. Those are detected, not assumed.

— What's included

What each plugin reads.

MySQL and MariaDB
Uptime, threads, questions, slow queries, connections — plus 28+ config variables and any override in conf.d.
PostgreSQL
Connections, active queries, database size, transactions, 16+ settings, and ALTER SYSTEM overrides via pg_settings.
Redis
Memory, clients, commands, hit rate, 14+ settings including maxmemory policy and persistence mode — and it detects Laravel, BullMQ, Sidekiq or Celery queues living in there.
Nginx
Active connections, reading/writing/waiting, accepts, handled, requests, 10+ directives, plus server and upstream block counts.
Apache, Docker, PHP-FPM
Discovered and charted the same way.
Attached on discovery
No config file, no per-host setup, no exporter sidecar.
— Works with

Connected capabilities

Service Discovery
Which services exist on each host — input to plugin attachment.
→
MySQL Slow-Log Viewer
Slow-log toggle and inline reader built on top of the MySQL plugin.
→
Smart Alerts
Build alert rules against plugin-specific metrics.
→
Auto-Recovery
Per-plugin restart policies for the services they cover.
→
— FAQ

Questions, answered honestly.

What credentials does a plugin need? +
MySQL / PostgreSQL: a read-only monitoring user (we ship the GRANT statements). Redis: no auth needed for INFO. Nginx: stub_status endpoint enabled.
What if my version is unusual? +
We test against the last three major versions of each. Older versions usually work but may miss the newest metrics.
Can I disable a plugin? +
Yes — per host or globally. The agent stops collecting and the platform stops charting.

Deep metrics, zero setup.

All plugins included on every plan.

Get early access Back to Monitoring