Requizon

Changelog

Every released version, with its date and what changed in it.

Newest first. Releases are published to the private Composer registry at requizon.composer.sh.

1.2.0 (15 November 2026)#

Added

  • Calls made through PHP's SoapClient are recorded. Construct RecordingSoapClient where you construct SoapClient, or add the RecordsSoapCalls trait to a subclass of an SDK's own client. See What gets recorded.
  • A SOAP call is counted under its operation, /BookingService.asmx/GetBooking, whichever client sent it. A search by the endpoint's URL still finds every operation. See Paths and table size.
  • XML request and response bodies, SOAP envelopes and faults included, are kept as XML and redacted by element and attribute name, so <wsse:Password> is stored as ***. The Details panel shows them indented. See Redaction and stored data.
  • Any alert detector can set its own idle_hours.

Changed

  • detectFailuresUsing() and redactUsing() receive an XML body as an array, such as $body['Envelope']['Body']['Fault']['faultstring'], where they were handed the raw string. See Failure detection.
  • A WS-Security nonce no longer makes every SOAP call unique on the list of calls that fail every time, and fingerprint.ignore can name XML elements.

Fixed

  • An alert no longer resolves, with a recovery sent, because its API stopped getting calls. It resolves once calls show it cleared, and one with no calls to go by resolves without a recovery after idle_hours. See Alerts.
  • One call getting through to an API that is down no longer resolves its alert. Clearing one takes as many calls as opening it did.
  • Rate limited and Timeouts alerts stay open while every call still ends that way, however few calls there are.
  • A Failure surge alert stays open while no call succeeds at an hour when some usually do, and Slowdown and Over latency target alerts stay open while the calls stay slow, however few there are.

1.1.0 (5 November 2026)#

Added

  • Every call keeps the path it was made to, /cbm/documents/123, beside the path it is counted under. The requests list shows it, and a row's details show the URL the call was made to, with the query redacted. See Paths and table size.
  • The Path filter takes a raw path or a whole URL pasted from a log, and lists the calls made to exactly that path, or with a query string, to exactly that URL. The overview has a search box for a URL too. See The dashboard.
  • Segments of the raw path that may be secrets are stored as ***, and a search by URL still finds those calls. paths.raw_unmasked, paths.raw_long_segments and REQUIZON_STORE_RAW_PATHS change what is kept, and Requizon::redactPathUsing() masks segments by value.

1.0.0 (9 October 2026)#

Added

  • Alerts. requizon:detect runs every five minutes and opens an alert when an API is unreachable, failing, answering 5xx, rejecting your credentials, rate limiting you, timing out, failing far more than usual for the hour, or slower than usual or than a target you set. See Alerts.
  • Alert notifications by mail, Slack and webhook, with reminders, recoveries, a cooldown, routes per severity and a daily digest. Set REQUIZON_NOTIFY_CHANNELS to turn them on, and run php artisan requizon:notify:test to check them.
  • An Alerts page on the dashboard, where alerts are acknowledged and muted. The header shows how many are open, and open alerts are listed above the overview and each API's paths page.
  • A row's details link to every request with the same parameters, so you can see whether a retry of a failed call went through.
  • The requests list filters by a query or body parameter, as key=value: order_id=123, customer.id=7. See The dashboard.

0.6.0 (7 October 2026)#

Added

  • An API's paths page lists the calls that failed every time they were made in the window, such as one wrong id sent over and over. fingerprint.ignore leaves out parameters that change on every call, and Requizon::fingerprintUsing() decides which calls count as the same. See Failure detection.
  • recording.success_bodies keeps the response bodies of successful calls, for every API or the ones you list, and success_body_sample_rate keeps a share of them. See Redaction and stored data.
  • REQUIZON_DISCOVERY=true records SDKs that get their HTTP client from php-http/discovery. See What gets recorded.
  • Guzzle 8 support, alongside Guzzle 7.

Changed

  • Requizon needs PHP 8.4 or newer.
  • A row's details load when you open them, so a page of failures with large bodies loads as fast as its table.
  • On MySQL and MariaDB, the overview's hourly chart went from 1.0 s to 0.34 s on 72 hours of production rollups, and the paths and requests pages are faster the same way.
  • A failure message that quotes a URL no longer includes its query string or any credentials in it.
  • A failed call's body that really is binary, such as an image or a PDF, is stored as its type and size. A text error sent under a file's Content-Type is still stored in full.
  • Http::fake() responses are timed by the clock instead of being recorded as 0 ms.

Fixed

  • A handler that throws before sending anything, such as Laravel's guard against stray requests, is no longer recorded as a 0 ms connection error.

0.5.0 (2 October 2026)#

Added

  • PostgreSQL, SQLite and MariaDB support. Requizon now runs on MySQL 8.0.19+, MariaDB 10.5+, PostgreSQL 9.5+ and SQLite 3.24+. See Installation.
  • Every dashboard page opens with the failures of the last 15 minutes by type, and the overview and paths tables sort whatever is failing now to the top. REQUIZON_RECENT_MINUTES changes the 15. See The dashboard.
  • paths.rewrite lets you choose the path to record for URLs whose identifiers the normaliser can't see, such as /files/4313261196505276_DSCF0122.jpg. See Paths and table size.
  • requizon:merge-paths applies your current paths config to calls already stored. --dry-run lists what would move. See Paths and table size.
  • recording.response_body_read_bytes sets how much of a response body is read for failure detection and redaction, separately from how much is stored. It defaults to 256 KB. See Failure detection.

Changed

  • A call shows up on the overview as soon as it is recorded, without waiting for the hour to roll up.
  • The paths page no longer runs PHP out of memory on a host with a path per call, and loads in about 0.8 s instead of 16.5 s. It shows up to dashboard.max_paths (500) paths, ranked by failures then requests, says when it cuts any, and always keeps a path failing right now.

Fixed

  • On MySQL and MariaDB, /files/abc and /files/AbC are now separate paths, and the slowest-paths chart no longer crashes on them.
  • The failure detector now reads a response body from the start, even if something else had already started reading it.

0.4.0 (20 September 2026)#

Changed

  • The request list counts the same period as the charts above it. A date range still replaces the window.
  • The request list pages by newer and older, with no page numbers, and a deep page loads as fast as the first. On 868k rows for one host, the first page went from 2.0 s to 12 ms.

Fixed

  • The overview was slow on a year of rollups. On 1.17M rows it went from 0.77 s to 10 ms.

0.3.0 (18 September 2026)#

Added

  • Request and response headers. recording.headers.request and recording.headers.response each take none, failures or all, defaulting to none for requests and failures for responses. Authorization, Cookie and api-key headers keep their name with the value masked. See Recording headers.
  • Redaction per API. An entry in the apis map can carry redact and redact_exact, so you can mask one provider's parameters without touching any other API. Requizon::redactUsing() covers what names can't express. See Redaction and stored data.
  • Query strings are stored for every method, and bodies whenever one is sent, so a POST keeps its ?expand[] and a GET with a JSON body keeps the body. The Details panel shows them as Query and Body.

Changed

  • Failed response bodies that parse as JSON or a form are redacted like requests, so a 401 from a token endpoint no longer keeps its credentials.
  • Tables are prefixed requizon_, so they can't collide with your application's own.

0.2.0 (15 September 2026)#

First public release. Requizon records every outbound call made through Laravel's HTTP client, and any Guzzle stack you push its middleware onto, with an hourly rollup and a dashboard at /requizon. See Installing Requizon.

Staying current#

# Move to the newest release your constraint allows
composer update boring-o11y/requizon

# Check what you are on
composer show boring-o11y/requizon

# List every published version
composer show boring-o11y/requizon --all

Common questions

What is the latest version of Requizon?

1.2.0, released on 15 November 2026. It records calls made through PHP's SoapClient, counts each SOAP call under its operation, keeps XML bodies as XML redacted by element name, and resolves an alert only once calls show it cleared. 1.1.0, ten days earlier, kept the path each call was made to and found a call by its URL.

How do I update Requizon to the latest version?

Run composer update boring-o11y/requizon. That moves you to the newest release your version constraint allows. Every purchase includes twelve months of upgrades.

Install Requizon today.

Checkout ends with your license key, and the installation guide takes it from there.