Comparing 2.3...1.14 · Sylius/Sylius
Commits on Feb 26, 2026
Commits on Mar 3, 2026
Commits on Mar 4, 2026
Commits on Mar 9, 2026
Commits on Mar 17, 2026
Commits on Mar 18, 2026
-
Telemetry improvements 1.14 (#18918)
| Q | A |-----------------|----- | Branch? | 1.14 <!-- see the comment below --> | Bug fix? | yes | New feature? | no | Related tickets | fixes #18905 | License | MIT <!-- - Bug fixes must be submitted against the 1.14 or 2.1 branch - Features and deprecations must be submitted against the 2.2 branch - Make sure that the correct base branch is set To be sure you are not breaking any Backward Compatibilities, check the documentation: https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html --> ### What changed **Per-query SQL timeouts** - Telemetry has been improved with per-query database timeouts. If any query exceeds the limit, it is immediately interrupted and falls back gracefully with empty data. The global query timeout (in milliseconds, default: 60000, minimum: 1000) is configurable via environment variable: ``` SYLIUS_TELEMETRY_QUERY_TIMEOUT=30000 ``` **Improved TelemetryListener caching** - Telemetry collection is now rate-limited. Once triggered, it will be skipped for the next hour, preventing concurrent and redundant data collection on frequent admin page loads. **PostgreSQL compatibility** - Fixed boolean comparisons in telemetry providers (`enabled = 1` → `enabled = true`)