Requizon docs
Requizon records every call your Laravel application makes through its HTTP client and serves a dashboard
for them at /requizon. Installing it
is the whole integration. These pages cover getting it in, then changing what it records, how it names and
groups what it records, and how long it keeps it.
Written for Requizon 1.1.
Getting started
Configuration
Configuration reference
Every key in config/requizon.php, its environment variable and its default.
What gets recorded
Everything through the Http facade, anything on a Guzzle stack you instrument, SDKs that find their client through discovery once you allow it, and nothing on a host you ignore.
Naming APIs
An unconfigured host names itself. Map hostnames to one API name, or resolve names from the request.
Paths and table size
How identifiers become :id, rewrite rules for the ones it misses, the allow-list that is the only hard bound, merging paths already stored, and the path each call was made to.
Failure detection
Connection errors, HTTP errors, the 200 OK with an error in the body that only your callback can spot, and calls that fail every time they are made.
Alerts
What opens an alert, how it stays open and clears, and how alerts reach mail, Slack or a webhook.
Redaction and stored data
Which parameters are masked, which keys you declare per API, which bodies are stored as they came, and how to keep successful bodies too.
Headers
Which headers are kept in each direction, how sensitive ones are masked, and how to narrow the list.
Retention and scheduling
The scheduled commands that build the rollup, bound the tables and run alerts, and how to run them yourself.
The dashboard
The overview, paths, requests and alerts pages, the failures-right-now panel, finding one call, and where the dashboard lives and who can open it.