The Voltir monitoring service uses a shared infrastructure stack for all clients, including VictoriaMetrics, VictoriaLogs, and Grafana. To ensure data isolation, the system relies on a numeric account_id. Incoming requests are authenticated via Nginx, which verifies tokens against the platform API before routing them to specific storage paths.
Grafana is configured with separate organizations for each client to prevent cross-tenant data access. Users are restricted to Editor or Viewer roles to block them from modifying data sources. The platform automatically deletes empty personal organizations created by Grafana when new users are added, preventing the accumulation of unused resources.
The vmalert service processes rules for all tenants from a single directory. To prevent a single misconfigured rule from crashing the entire alerting system, the platform now validates rule syntax, durations, and Go templates before saving. Atomic updates and inter-process locking ensure that only valid configurations are reloaded.
Resource cleanup is managed by a centralized module that handles the removal of rules, Grafana organizations, and storage data. A background synchronization process runs hourly to identify and remove orphaned resources. VictoriaMetrics series are deleted twice, with a 90-second interval, to account for metrics written during the deletion process.
