Skip to content

Managed operations

Infrastructure operations

Change management, patching, configuration versioning, capacity and day-to-day operations.

Architecture

Architecture

  1. 01MonitorMetrics, logs, synthetics
    • Zabbix
    • Prometheus
    • Blackbox
  2. 02DetectThresholds and anomalies
    • Alertmanager
    • Grafana Alerts
  3. 03TriageSeverity, impact, owner
    • Runbook
    • On-call
  4. 04RespondIsolate and restore
    • Change window
    • Rollback
  5. 05ResolveVerify and report
    • RCA
    • SLA report
  6. 06ImproveRules, automation
    • Alert tuning
    • Runbook update
Incident lifecycle — from monitoring through to improvement

Operator consoles

Operator consoles

These exact systems run on the group's own infrastructure — the screenshots are processed before publication.

Blurred Proxmox Datacenter Manager — aggregate state of nodes, virtual machines, containers and backup servers.

8 clusters from one interface

Proxmox Datacenter Manager brings independent Proxmox VE clusters into one place. In our own infrastructure it manages 8 of them, spread across separate physical locations — 3 of those outside Georgia. The frame also shows the scale: 211 nodes online, 1,480 virtual machines and 127 containers — one view, one procedure.

Proxmoxmulti-clustermulti-sitePBS
Blurred vSphere Client — the virtual machine inventory and one machine's resource usage.

vSphere — the cluster, its hosts and the workloads on it

A vCenter with several ESXi hosts and the services placed on them: web, billing, a domain controller, backup agents. This is the environment where VMware and Proxmox coexist — part of it still on vSphere, part already migrated. One team operates both, under one backup policy.

vSphereESXivCentermigration
Blurred backup dashboard showing protection status and a storage usage chart.

Backup and recovery

Centralised backup for virtual and physical systems: protection status per machine, the storage usage trend, and a separate list of hosts that stopped reporting. That last list is what matters — a backup nobody watches is not a backup.

VM backupretentionrestore testalerting
The WireGuard Portal interface administration screen — peer counts and interface parameters; keys and addresses are redacted.

WireGuard Portal — peers managed in one place

WireGuard is fast, but by default it is administered through config files — and by the twentieth peer that is a problem. The portal centralises key and peer management, adds self-service provisioning and shows who is connected right now. Interface state, MTU, DNS and keepalive on one screen.

WireGuardpeer managementself-serviceMikroTik

Capabilities

Capabilities

Every item is marked: verified production experience, or engineering capability.

24/7 network monitoring

Proven

The group's own ISP and datacenter run continuously — same processes, same tooling.

  • Zabbix
  • Prometheus
  • Grafana

Severity-based incident response

Proven
  • Runbooks
  • On-call rota

SOC — event correlation

Capability

SIEM rules, detection content and incident response playbooks.

  • Wazuh
  • Graylog
  • OpenSearch

Co-managed mode

Capability

Your team keeps control; we cover the shifts and the escalation path.

ITSM integration

Capability

Two-way sync with your ticketing system.

  • Webhooks
  • REST API

Telegram / PagerDuty escalation

Proven
  • Telegram Bot API
  • Alertmanager

Path monitoring and loss detection

Proven

Latency and packet loss to every critical destination — including cache servers hosted inside individual operators. That is how you tell whether the fault is in our network, in transit, or at the content provider.

  • OpenPath
  • ICMP / TCP probes
  • per-ASN

Technology stack

Technology stack

Monitoring
ZabbixLibreNMSPrometheusGrafanaBlackbox
In-house tooling
OpenPathnoc.com.ge
Logging
GraylogOpenSearchLokiVector
Security
WazuhFortiGateSuricata
Alerting
AlertmanagerTelegramPagerDuty

Engagement model

Engagement model

Co-managed

NetWizard and your in-house team together, with split responsibility.

Fully managed

We own the agreed operational scope end to end.

Critical operations

24/7 monitoring, response and severity-based escalation.

Retainer

Monthly engineering hours — specialist access on demand.

FAQ

FAQ

How do you access our infrastructure?

Named accounts only, with MFA, logged sessions and agreed change windows. Details are in the Trust Center.

What SLA do you offer?

The SLA is defined per service plan: severity-based acknowledgement, response and escalation targets are fixed in the contract.

Can you work with our existing tools?

Yes. If you already run Zabbix, Prometheus, Grafana or a SIEM we operate on it, correcting the configuration where needed.

Tell us about your infrastructure