Where Does Highlight Store Sessions?
Where self hosted Highlight keeps sessions in database on Linux servers. Full paths are listed below.
Last updated
Highlight is error monitoring with server storage. The database holds sessions, errors, and users. Object storage holds replay blobs beside it.
Same database plus storage means same replays. Exact paths vary by Docker installs. Keep backups of both together. One without the other restores sessions without video. For moves, stop SDK intake first to avoid partial writes during copies. Screenshots of settings help when support asks for reproduction steps later. Check the in app storage readout when sizes look wrong on different releases.
Where Highlight Errors stores this, by platform
/var/lib/highlight (database plus storage, paths vary)
Sessions live in the server database with replays in object storage. Back up both together stopped. Match releases before restore.
Frequently asked questions
How do I migrate Highlight to a new server?
Back up the Highlight database plus object storage with services stopped, then install the same release on the new server before restore. Sessions follow the database. Mixed releases can refuse old schemas, so match versions first.
Does Highlight back up sessions?
Yes, in the server database per session with replay history attached. The host holds a working copy plus SDK cache. Views rebuild after restore. Export JSON sessions from dashboards for records, since volumes alone are working state.
Notice an outdated path? Let us know.