> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vms.verolabs.co/llms.txt
> Use this file to discover all available pages before exploring further.

# VMS Overview

> Vero Monitor Service operations documentation

<div style={{ width: '100%', height: 240, marginBottom: 32, borderRadius: 16, overflow: 'hidden', position: 'relative' }}>
  <video style={{ width: '100%', height: '100%', objectFit: 'cover' }} autoPlay loop muted playsInline>
    <source src="https://mintcdn.com/vero-35a9bc05/YT70Sr2qWE1qMbL1/images/bg_video.mp4?fit=max&auto=format&n=YT70Sr2qWE1qMbL1&q=85&s=280fdae232cc55fac656d71686b9271e" type="video/mp4" data-path="images/bg_video.mp4" />
  </video>
</div>

<div style={{ width: '100%', height: 4, marginBottom: 24, borderRadius: 2, background: 'rgba(0,0,0,0.08)' }}>
  <div style={{ width: '25%', height: '100%', borderRadius: 2, background: 'linear-gradient(90deg, var(--accent-primary) 0%, var(--accent-light) 50%, var(--accent-dark) 100%)' }} />
</div>

Vero Monitor Service (VMS) is the setup and operations documentation for end-to-end monitoring across infrastructure, services, user checks, and business flows.

<CardGroup cols={3}>
  <Card title="VMS Master" icon="server">
    Set up the central control plane for dashboards, alerting, synthetic checks, topology, metric storage, and operator access.
  </Card>

  <Card title="Agent Collector" icon="satellite-dish">
    Deploy collectors close to monitored systems to capture host metrics, processes, ports, service health, and connections.
  </Card>

  <Card title="Troubleshooting" icon="screwdriver-wrench">
    Standardize fixes for missing collectors, stale dashboards, alert noise, pre-market failures, and health-check issues.
  </Card>
</CardGroup>

## 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 all hosts and system infrastructure | 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 status, applications, 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

<Steps>
  <Step title="Understand the VMS scope">
    Start with the overview to understand the four monitoring layers, VMS components, and Basic/Advanced boundaries.
  </Step>

  <Step title="Set up the VMS master">
    Use the master guideline to prepare namespace, storage, secrets, ingress, dashboards, alerting, and readiness jobs.
  </Step>

  <Step title="Set up agent collectors">
    Use the collector guideline to deploy agents near hosts and services, apply standard tags, and confirm data reaches the master.
  </Step>

  <Step title="Troubleshoot operations">
    Use troubleshooting for collector, dashboard, alert, synthetic check, and connection issues.
  </Step>
</Steps>