Monitoring
Continuous visibility over any network asset, with automatic alerts and human contact from the NOC for any outage.
Service overview
Monitoring is ACT's service dedicated to watching the health of any network asset and alerting when something goes off-expected, without including remote management or corrective action on the infrastructure. It's aimed at clients who manage their own infrastructure, or have only part of it under ACT management and want visibility over the remaining network assets. When an asset is already under ACT management, its monitoring is already included automatically: this service applies to the other network assets the client wants to monitor without contracting full management.
Any network asset
Servers, internet links, switches, routers, UPS units, storage, applications, and sites: any asset compatible with an agent, SNMP, or ping check.
Alerting with human action
Automatic notification via WhatsApp, Telegram, or email, with a ticket opened and human contact from ACT's NOC on incidents active for more than 10 minutes.
Monitoring, not management
Full focus on identifying and alerting quickly, so the decision to act always stays with the team responsible for the infrastructure.
What is monitored
The collection method depends on the technology available on each asset, from a full agent to a simple network availability check.
| Method | When it's used | What it enables |
|---|---|---|
| Zabbix agent | Assets where the agent can be installed (servers, workstations) | Full monitoring of resources and services |
| SNMP | Network equipment that supports the protocol (switches, routers, UPS units) | Monitoring of equipment metrics, no agent required |
| Ping check | Assets without SNMP and without agent support | Confirms only whether the asset is responding on the network |
The contracted package defines the number of monitored assets; the client indicates which network assets should be included.
Alerts and incident response
Every outage active for more than 10 minutes gets human contact from the NOC, not just an automatic notification left unattended.
| Stage | What happens |
|---|---|
| Alert triggered | Automatic notification via WhatsApp, Telegram, or email, per client preference |
| Ticket opened | Automatically, after 10 minutes of active outage |
| Human contact | A NOC technician reaches out via WhatsApp, reports the outage, and investigates the cause with the client, for documentation |
| Next action | ACT helps identify the root cause; next steps are coordinated with the client based on the source of the problem |
Incidents resolved in under 10 minutes do not trigger human contact, only the alert record.
Service scope and limits
How infrastructure access works: the service's focus is identifying and alerting; the decision on fixes stays with the team responsible for the asset. In practice, ACT's access is limited to deployment, to configure the agent or guide the client's IT team to do so.
Exception: configured automations.
Beyond the standard alert, it's possible to schedule an automatic action for a specific, already-known scenario, for example, restarting a service when it stops responding, or freeing up space when disk usage hits a critical threshold. Each automation is agreed and approved in advance with the client, asset by asset: it's not general access by ACT to the infrastructure, but a programmed response to a specific situation.
Deployment
| Scenario | How it's done |
|---|---|
| Servers and workstations | Zabbix agent installed directly on the asset |
| SNMP-capable equipment (switches, routers, UPS units, etc.) | Zabbix Proxy hosted on the client's local network: the client provides access to a Linux host, and ACT handles the full configuration |
| Assets without agent and without SNMP | Availability check by ping |
Beyond the initial setup, no other type of access to the client's infrastructure is required.
Specifications
| Dashboard | Zabbix dashboard customized to the client's reality, open to suggestions and adjustments |
| Notification channels | WhatsApp, Telegram, and email, per client preference |
| Support hours | Monday to Friday, 8:30am–12:00pm and 1:00pm–5:30pm, excluding national and local holidays |
| Response: Emergency | Up to 4 business hours (system fully down), via remote access |
| Response: Urgent | Up to 6 business hours (system partially down), via remote access |
| Response: Specific cases | Up to 12 business hours (not affecting the system), via remote access |
| Response: Rescheduling | Up to 24 business hours, via remote access |
| Capacity | Number of monitored assets sized by commercial proposal |
Want to know if Monitoring solves what your operation needs?
Talk to ACT and understand, with clarity, how this solution fits your environment.
Talk to ACT