benecaster_support_mode_log_limit
Filters the maximum number of benecaster_debug_log entries bundled into the diagnostic snapshot when an admin clicks “Send diagnostic log to Benecaster support”.
When It Fires
When building the diagnostic snapshot inside POST /benecaster/v1/tools/support-mode/send-diagnostic-log, immediately before querying benecaster_debug_log for the most recent N rows.
Parameters
| Name | Type | Description |
|---|---|---|
$limit |
int | Maximum number of log entries to include. Default: 200 |
Return Value
Return the modified $limit as an integer. Values less than 1 are ignored — the endpoint falls back to the default of 200.
Notes
This is a Free filter. It fires regardless of license status.
The snapshot is gzipped before being POSTed to the license server, so payload size is roughly proportional to the number of entries — not a 1:1 byte relationship with the raw log rows. That said, verify with the Benecaster support team before raising the limit well past a few thousand entries, as unusually large snapshots may affect processing time on the server side.
This filter is most useful for add-ons that emit a high volume of verbose entries when Support Mode is active. If your add-on’s debug output is concentrated at a specific point in time (e.g. during a feed sync job or a batch transcription run), raising the limit ensures that output is still present in the snapshot rather than being pushed out by more recent entries.
Example Usage
Raise the limit to 500 entries:
add_filter(
'benecaster_support_mode_log_limit',
static fn() => 500
);
Related
expand-the-support-mode-diagnostic-snapshot— full recipe with usage guidancebenecaster_support_mode_enabled— hook to enable verbose logging when Support Mode turns on