Sailfish docs
Sailfish reads MySQL's performance_schema every five minutes, keeps what moved past the restarts that
reset it, and serves a dashboard for it at
/sailfish. It can read a Redis server's
INFO beside it, and count what your
application does with its cache. These pages cover getting it in, what it records and for how long, and the
events it sends when something changes.
Written for Sailfish 0.4. What changed
Getting started
Configuration
Using Sailfish
The dashboard
What each page of /sailfish shows, and the two gates that decide who sees it.
What gets recorded
The sailfish_* tables, where each counter comes from, and how deltas survive the ways performance_schema resets.
Retention and rollups
Seven days of five-minute snapshots, ninety of hourly ones, then daily ones for good.
Statement digests
MySQL 8.0 gives no digest to native prepared statements, which is what Laravel sends by default.
Redis and the cache
Redis
Name a Redis connection and every collection reads its INFO: what each command costs, hits against misses, memory and when it runs out, keys for each database, and fourteen events.
Cache
What the application does with its cache, for each group of keys: hits and misses, how long a value took to generate, entries generated twice at once and entries never read.