Where Does HyperDX Store Sessions?
Where self hosted HyperDX keeps telemetry in database on Linux servers. Full paths are listed below.
Last updated
HyperDX is session replay with server storage. The database holds sessions, errors, and users. ClickHouse volumes hold events beside it.
Same database plus volumes means same replays. Exact paths vary by Docker installs. Keep backups of both together. One without the other restores sessions without events. For moves, stop collectors 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 HyperDX Sessions stores this, by platform
/var/lib/hyperdx (database plus volumes, paths vary)
Sessions live in the server database with events in ClickHouse volumes. Back up both together stopped. Match releases before restore.
Frequently asked questions
How do I migrate HyperDX to a new server?
Back up the HyperDX database plus ClickHouse volumes 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 HyperDX back up session history?
Yes, in the server database per session with event history attached. The host holds a working copy plus collector 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.