2025.10
Highlights
This release contains two new features and a few improvements. The new features are multi location uptime monitoring and data retention. Multi location monitoring is essential to eliminate false positives and gives insight on latency across the world. Up until now Vigilant did not delete your data, this means an ever-growing database which now gets automatically cleaned. For self-hosters the amount of days per monitor can be configured in the environment file and for users of the hosted version it is dependand on your plan.
Then there are a few improvements to the existing functionalities such as the ability to ignore broken URL's so that you do not get notified each time your website is crawled. The menu has also been reworked to be more compact and notifications now show a small description on what they do on the frontend.
Breaking Changes
This release requires you to add an additional container to your `docker-compose.yml` to accompany for the changes in the uptime monitor.
With the new data retention feature Vigilant will delete old data, you may adjust this in your environment file. See the data retention documentation for more information.
New Features
Multi location uptime/latency monitoring
Ignore broken URLs
Data retention to automatically delete old records
New notification type that detects short latency peaks
Upgrading
Add the `outpost` container to your compose file. See the deployment documentation for an example.
Minor Changes & Fixes
Adjusted menu structure
Improve the way CVE's are matched
Fix bug where notification conditions could not be saved
Fix bug in the notification menu active state
Notification types and conditions can now show a description in the frontend to make it more clear what they do
Start Monitoring within minutes.
Get started with Vigilant in a few minutes, sign up, enter your website and select your monitors.
Vigilant comes with sensible defaults and requires minimal configuration.