Crash Snapshot Pro

Crash Snapshot Pro – Advanced Production Error Diagnostics for PrestaShop 9

Crash Snapshot Pro extends production-safe error capture with diagnostic tools intended for stores where knowing that an error happened is not enough. It adds likely-source detection, database diagnostics, recent-change correlation, downloadable support bundles, filtered alerts and advanced incident controls on top of the same privacy-conscious capture foundation.

Detect the likely technical source

Pro analyzes sanitized incident information and stack paths to classify the likely source as a module, theme, PrestaShop core, vendor dependency, database or unknown source. The dashboard shows the detected source together with a confidence level.

Source detection is intentionally presented as a diagnostic heuristic, not proof of causation.

Correlate incidents with recent changes

Crash Snapshot Pro tracks selected technical changes and can show them next to an incident when they fall inside the correlation window. Tracked events include module install, uninstall, enable, disable and upgrade actions, as well as Smarty, compile and Symfony cache clears and Crash Snapshot configuration changes.

This helps answer a common production question: “What changed shortly before the error started?” Temporal correlation is shown as a clue, not as a guaranteed root cause.

Classify SQL and database failures

Database-related exceptions can be inspected for SQLSTATE and database error-code information. This adds structured context to problems such as missing columns, schema mismatches and other SQL failures without pretending that an error code alone proves the underlying cause.

Generate a sanitized support bundle

For an incident, Pro can build a downloadable ZIP support bundle containing sanitized diagnostic information, environment context and available recent-change information. This gives a developer or support engineer a compact technical package without requiring a full debug page or raw request dump.

Send filtered email and HTTPS webhook alerts

Configure an email address and/or HTTPS webhook for new incidents. Alerting can be restricted to new fingerprints, critical errors, Front Office / Back Office context, a specific detected module/source, occurrence thresholds and an occurrence window. Cooldown state helps prevent repeated notifications from becoming alert noise.

Use advanced incident filtering

In addition to the standard incident search and review workflow, Pro can filter by HTTP status, minimum occurrences, date range, source type, source/module name, error type, exception class and theme.

Control retention and spool limits

Pro exposes configurable retention periods, maximum incident counts, maximum spool-file count, spool disk usage and per-incident file-size limits. Default Pro settings keep a larger diagnostic history than Lite and can be adjusted to the store environment.

Expanded self-test and capture health

The safe Pro self-test verifies exception capture, synthetic database/template failures, spool write/import, privacy scrubbing and configured alert channels. Synthetic incidents are clearly marked so they can be removed after verification.

Support bundles and Module Hub integration

Support bundles can be downloaded locally from the Back Office. Pro also contains an opt-in Module Hub sharing integration boundary, but remote sharing is disabled by default and requires a compatible transport adapter. The local diagnostic workflow does not depend on Module Hub.

Compatibility and important limitations

• Designed for PrestaShop 9.
• Requires PHP 8.1+.
• No PrestaShop core override is used.
• Likely-source detection and recent-change correlation are diagnostic hints, not proof that a particular module or change caused an incident.
• Errors before PHP/PrestaShop/module bootstrap, hard PHP-FPM crashes, OS out-of-memory kills and upstream 502/503 failures may occur before Crash Snapshot can capture them.
• Uninstall keeps captured incident data; destructive purge is a separate explicit action.

Frequently asked questions

Is the “Likely source” result guaranteed to be the root cause?

No. Pro uses sanitized stack paths, error context and diagnostic signals to rank a likely source. The result is a troubleshooting clue and is deliberately not presented as proof.

What is included in a support bundle?

The bundle is designed to contain sanitized incident diagnostics, environment information and available recent-change context. Sensitive request payloads are not intentionally added as a raw dump.

Can Pro alert only on important incidents?

Yes. Alerts can be filtered by new fingerprint behavior, critical-only mode, context, detected source and occurrence thresholds, with an occurrence window and cooldown handling.

Does Pro require Module Hub?

No. Local capture, diagnostics, source detection, support bundles and alerts work independently. Module Hub sharing is an optional integration boundary and is disabled by default.

What happens to Lite incidents after enabling Pro?

Crash Snapshot Pro uses the shared Crash Snapshot incident storage and extends the schema with Pro diagnostic data. Existing incident history is retained rather than starting a separate Pro database.