Where Does Parca Store Profiles?
Where self hosted Parca keeps profiles in database on Linux servers. Exact folders are covered below.
Last updated
Parca is continuous profiling with server storage. The database holds profiles, symbols, and targets. Agents send pprof data on schedule.
Same database means same flame graphs. Exact paths vary by Docker versus binary installs. Keep backups on schedule. One missing table restores targets without history. For moves, stop agents first to avoid partial writes during copies. Check the in app storage readout when sizes look wrong on different releases. When in doubt, verify paths inside the app before trusting a remembered folder.
Where Parca Profiling stores this, by platform
/var/lib/parca (database, paths vary by install)
Profiles live in the server database with symbol history. Back up the database stopped. Match releases before restore. Agents send pprof on schedule.
Frequently asked questions
How do I migrate Parca to a new server?
Back up the Parca database with services stopped, then install the same release on the new server before restore. Profiles follow the database. Mixed releases can refuse old schemas, so match versions first. Keep object storage keys separate.
Does Parca back up profiles?
Yes, in the server database per profile with symbol history attached. The host holds a working copy plus agent cache. Views rebuild after restore. Export pprof files from the UI for records, since the data directory alone is working state.
Notice an outdated path? Let us know.