NOC · monitoring · automation
ISP / WISP operations
We help operators run their network more calmly — monitoring that knows before customers do, runbooks the on-call engineer actually uses, and automation that removes manual work.
- Monitoring that makes sense
- Zabbix or Prometheus/Grafana tuned for an operator — sensible thresholds, dependencies and alerts that don't bury the on-call engineer.
- NOC design
- Roles, shifts, escalations and runbooks. Who does what when a link drops at 3 a.m.
- Automation
- Config backups, compliance checks and routine changes through Ansible and scripts — not by hand on every device.
- Advisory on demand
- Monthly hours for a second opinion, change review and support during major incidents.
Scope
What we do
From rolling out monitoring to ongoing advisory for your NOC team.
Stack
- Zabbix
- Prometheus
- Grafana
- Ansible
- NetBox
- Oxidized
Monitoring and visibility
- Rolling out or cleaning up Zabbix and Prometheus/Grafana monitoring
- Network inventory and documentation (e.g. NetBox) as the source of truth for monitoring and automation
- Dependencies between devices, so one failed link doesn’t raise a hundred alerts
- NOC dashboards and availability reports for management
NOC and procedures
- NOC organisation: roles, shifts, escalations
- Runbooks for the most common incidents
- Procedures for planned work and customer notifications
- Post-incident reviews after major outages — what happened and what we change
Automation
- Automatic config backups and change tracking (e.g. Oxidized)
- Ansible and scripts for routine changes across many devices
- Config compliance checks against your standard
How we work
Visibility first, then procedures, then automation.
- 01
Operations review
How you learn about problems today, who responds and how long it takes. We measure, we don't assume.
- 02
Monitoring
We roll out or clean up monitoring — inventory, dependencies, thresholds, alerts and NOC dashboards.
- 03
Procedures
Runbooks for the most common incidents, escalations and customer communication.
- 04
Automation
What repeats goes to scripts, with change review and an audit trail.
Questions
Frequently asked
We have Zabbix, but nobody watches the alerts. Can that be fixed?
That is the most common case. We usually reduce the number of alerts first — dependencies and thresholds — and only then add new checks.
Will you take over on-call for us?
We don't run your NOC for you, but we help you organise it and can act as second-line support for major incidents, by agreement.
Can you work with our existing tools?
Yes. We don't replace tools for the sake of it — we build on what works and replace only what slows you down.
Too many alerts, too little insight?
Show us what an incident looks like today — we'll suggest what to fix first.