Vero Monitor Service (VMS) is the setup and operations documentation for end-to-end monitoring across infrastructure, services, user checks, and business flows.
VMS Master
Set up the central control plane for dashboards, alerting, synthetic checks, topology, metric storage, and operator access.
Agent Collector
Deploy collectors close to monitored systems to capture host metrics, processes, ports, service health, and connections.
Troubleshooting
Standardize fixes for missing collectors, stale dashboards, alert noise, pre-market failures, and health-check issues.
Four-layer monitoring model
| Layer | Question to answer | Main signals | Primary users |
|---|---|---|---|
| Infrastructure | Are hosts, containers, and networks healthy? | CPU, memory, disk, network, host status, container restart | Infrastructure / Platform |
| Service | Which service or dependency is not responding? | Process, TCP/HTTP health, service-to-service connection, basic latency | Application / Technical |
| User | Are synthetic checks and pre-market readiness passing? | Step status, run time, 08:30 readiness result | Operation |
| Business Flow | Which flow has the suspected issue? | Topology, path health, node/edge status by flow | Management / Business owner |
Deployment scope
| Area | Basic Scope | Advanced Scope |
|---|---|---|
| Infrastructure | Host-level monitoring for Core / WEB / Mobile and satellite systems | Basic plus deeper analysis when approved |
| Service | Process, open port, TCP/HTTP probe, dependency connection | DBM, MQM, APM, distributed tracing |
| User | Synthetic checks and 08:30 pre-market readiness | Synthetic web, RUM, and extended post-change verification |
| Business Flow | Topology dashboards based on existing signals | Trace, log center, and runbook support for deeper triage |
| Deliverable | Dashboards, alert catalog, readiness report, handover | Extended dashboards, log/tracing, runbooks, advanced observability |
VMS components
| Component | Role |
|---|---|
| Vero Stack Monitor | Central control plane for dashboards, alerting, topology, and operations |
| Vero Metric Collector | Collects host metrics, process status, service health, connections, and custom probes |
| Vero Dashboard | Shows overall system, Core / WEB / Mobile detail, satellite systems, and KPI/SLA |
| Vero Alert | Manages severity, owner, routing, escalation, and maintenance windows |
| Vero Synthetic Engine | Runs scheduled synthetic checks, 08:30 readiness checks, and post-change checks |
| Log Center | Centralizes, indexes, and searches logs when included in advanced scope |
| Vero Tracing / APM / RUM | Adds root-cause analysis when systems have approved instrumentation |
| Vero Runbook Engine | Request -> Approve -> Bot Execute workflow for approved actions |
How to use these docs
Understand the VMS scope
Start with the overview to understand the four monitoring layers, VMS components, and Basic/Advanced boundaries.
Set up the VMS master
Use the master guideline to prepare namespace, storage, secrets, ingress, dashboards, alerting, and readiness jobs.
Set up agent collectors
Use the collector guideline to deploy agents near hosts and services, apply standard tags, and confirm data reaches the master.