Vigilbase runs managed services for you on vendor platforms such as Cloudflare, NinjaOne and Afi. Vigilbase One is where you see the state of those services, follow monitoring of your domains, ask for changes and get help. You read in One; changes to your services go through change requests that Vigilbase prepares, reviews and verifies.
Your services
Your Vigilbase team sets up each managed service and links it to your organisation. Once a service is active, it gets its own page under Services in the sidebar, and Home summarises what is covered. See Managed services.
The Environment map at one.vigilbase.com/fabric shows your services and assets, and how they are covered, on one map.
Monitoring
Watchdog checks your public domains for uptime, latency and SSL, and scans them for HTTPS, header, DNS and email security issues. Your Vigilbase team chooses the targets. You follow the results on Monitoring. See Watchdog.
Changes
Every change Vigilbase makes to a managed service goes through a change request:
You ask for the change, in One, through your Vigilbase team or by asking Vigil.
Vigilbase prepares an exact plan, with the current and desired state, impact, rollback and verification.
The plan is approved according to your organisation's approval policy.
Vigilbase executes it after checking the live state again, then verifies the result.
Help
For questions about your services, ask Vigil. For anything else, or to talk to a person, use Support.
What Vigilbase reads, and what it changes
One and Vigil read the state of your services from the vendors' platforms to show it to you. Vigilbase changes a managed service only through an approved change request. Asking Vigil a question does not change anything.