Built with harnsy — the Buggregator team runs its AI agents in harnsy.
Before you upgrade
- Sentry requests larger than 64 MB are no longer stored. The limit applies to the body as sent and after unpacking (gzip, deflate, br, zstd); the zstd window is capped at 8 MB. A body over the limit is refused, and a warning is logged when an unpacked one is dropped. Real Sentry events are far smaller; this stops a tiny compressed request from making the server allocate hundreds of megabytes. (#426, #429)
Added
- Sentry: a project per service, even with a numeric DSN. The JavaScript SDKs only accept a number as the DSN project id. Now the public key before
@can name the project:http://billing@buggregator:8000/1lands in the projectbilling. The key picks a project only if that project already exists (declared underprojects:inbuggregator.yaml, or created earlier). An unknown key and the keysentryused in our docs keep going todefault, and no project is created from a key. Order: project in the DSN path, thenX-Buggregator-Project/ Basic Auth, then the key, thendefault. (#431, closes #430) - SMS: Twilio's send API. Twilio clients, including Symfony's Twilio notifier, can now send SMS to Buggregator:
POST /2010-04-01/Accounts/{sid}/Messages.jsonanswers like Twilio (201with a messagesid, or400with Twilio error codes 21602/21603/21604 when Body, From or To is missing; the message is still stored)./sms/twiliono longer requiresMessageSid. Symfony's SMS bridges always use HTTPS, so put a TLS proxy in front of Buggregator for them. (#423)
Fixed
- Projects from
buggregator.yamlexist from the first start. They were inserted before the database tables were created, so with the default in-memory database they never appeared until an event created them. (#433, closes #432) - Sentry timestamps are returned in UTC with an explicit
Zby the Sentry API, so the UI shows the right local time. Before, times in the Sentry views were shifted by the viewer's UTC offset (an error that had just arrived could show as «3 hours ago»). Thanks to @tsan88 for the fix. (#353) - HTTP proxy:
- Stored bodies compressed with gzip, deflate, br or zstd are now decoded, also when
Content-Encodingcomes on several header lines. (#424, #425) - Large bodies pass through whole; only the stored copy is capped. (#427)
- One shared upstream connection pool instead of a new one per request (idle connections no longer pile up), and HTTP/1.0 clients no longer get chunked answers they cannot read. (#429)
- Stored bodies compressed with gzip, deflate, br or zstd are now decoded, also when
Changed
- README: setup snippets for the Sentry JavaScript, Python and Go SDKs. (#422)
Upgrade
Replace the binary or pull the new image. There are no new database migrations. Bundled UI: frontend 1.37.1.
What's Changed
- feat(sms): accept Twilio's send API and answer like Twilio by @butschster in #423
- docs: Sentry SDKs for JavaScript, Python and Go in the README by @butschster in #422
- fix(proxy): store gzip, deflate and br bodies decoded by @butschster in #424
- fix(proxy): decode zstd and Content-Encoding split over header lines by @butschster in #425
- fix(sentry): cap decompressed payloads at 64 MB and the zstd window at 8 MB by @butschster in #426
- fix(proxy): pass whole bodies through, cap only the stored copy by @butschster in #427
- fix(proxy): share one upstream Transport; no chunked to HTTP/1.0 clients by @butschster in #429
- fix(sentry): return timestamps with an explicit UTC zone by @tsan88 in #353
- feat(sentry): route events to a project by the DSN public key by @butschster in #431
- fix: seed config projects after the migrations by @butschster in #433
- chore: bump frontend version to 1.37.1 by @butschster in #434
Full Changelog: v2.9.0...v2.10.0