Where Does Vigil Store Monitors?
Where self hosted Vigil keeps monitors in config on Linux servers. Exact folders are covered below. More below.
Last updated
Vigil is status monitoring with file config. Your monitors live in its config file. Probes run on schedule without a database.
Same config file means same monitors on any machine with Vigil installed. Exact file names are stable across late releases. Keep full backups before upgrading. For moves, copy the config file. Partial setups miss webhook URLs that alerts depend on. 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 Vigil Uptime stores this, by platform
/etc/vigil (config file, no database)
Monitors live in the Vigil config file. Copy it for moves. No database exists to dump. Match releases before importing old formats.
Frequently asked questions
How do I migrate Vigil to a new server?
Back up the Vigil config file with services stopped, then install the same release on the new server before restore. Monitors follow the config. Mixed releases can refuse old formats, so match versions first. Keep webhook URLs separate from shared copies.
Does Vigil keep history?
No. Vigil reads monitors from its config file without keeping history itself. The server holds the config plus probe cache. Reinstalls reset views but never touch an external history store. Treat the config file itself as the backup.
Notice an outdated path? Let us know.