Bugsink 1.3: Out-of-DB Event Storage

Klaas van Schelven
Klaas van Schelven; Febuary 20 - 1 min read
Bugsink 1.3 release

Bugsink 1.3 is here! The biggest change? An optional way to store event data outside the database, making large-scale setups more efficient.

By moving full event JSON storage out of the main DB, you get:

  • More portable backups – Depending on event size, database impact is reduced by a factor of 50.
  • Fewer physical storage limits – Avoid disk size or max file constraints on your database.

This change is expected to speed up migrations, especially on SQLite, which performs full table copies. However, ingestion speed remains largely unchanged.

Read the full story about out-of-DB event storage.

Further Features

Beyond storage improvements, Bugsink 1.3 adds various UI, performance, and usability enhancements:

  • Issue list pagination – Navigate large issue lists more easily (and for installations with more than thousands of issues, keep the UI responsive).

  • Event-detail UI for Logentries – Now shows logentry.message and logentry.params.

  • Support for top-level message in events (#43).

  • Thousand-separators for counts – Improved readability in the UI when dealing with (well) over 1,000 events.

  • CORS support – By adding CORS support, JavaScript SDKs show fewer warnings.

Command-line improvements

  • nuke_events – More consistent behavior, better confirmation.
  • make_consistent – Affects more cases and runs in a transaction.
  • migrate – Always shows timings.
  • showstat – Now includes digestion_speed.
  • send_welcome_email – Now available as a command.

Upgrading to Bugsink 1.3

Bugsink 1.3 is ready to use today. Try it out and let us know what you think!

See the full changelog on GitHub

Upgrade now or install Bugsink for the first time.