01
Scope and responsibilities
We list critical services, locations, dependencies and current problems. We agree quality and availability measures, service hours, alert recipients and how urgent matters are passed on outside business hours.
IT service availability
IT monitoring and Nagios
We implement monitoring for servers, networks, applications and backups. Each alert is linked to a service, priority and person responsible for responding. We agree service hours, test notifications and hand over the configuration with operating instructions.
Trusted by
Companies and institutions that need stable IT.
What is happening to your IT services?
Monitoring helps establish whether an outage or slowdown involves a server, network or application. We start with services important to your business and their dependencies, on premises, in the cloud or across both. We check resources, website, email, DNS, VPN, database and Microsoft 365 availability, and certificates. Sign-in or application checks can be added within the agreed scope. Infrastructure checks, network performance monitoring (NPM) and application performance monitoring (APM) answer different questions; traffic analysis does not replace code-level diagnosis. We separately agree measurements from real user sessions (RUM), temperature and humidity readings from server-room sensors, and checks of end-of-day processing (End Of Day). We select data sources and assessment criteria; session data scope, access and retention are agreed before collection starts.
Services connected with monitoring
We agree what to measure and how problems will be handled. These links lead to services that can be combined with the monitoring project.
System administration
Support for Windows and Linux servers, virtual machines, storage and UPS. Monitoring covers agreed CPU, memory, disk, process and service parameters.Network audit
A network review when access problems arise. Alerts about latency, packet loss or a saturated link help identify areas to examine.Backup and recovery
Checking failed jobs, missing backups, repository capacity and restore-test results. A successful backup status alone does not confirm that data can be recovered.IT helpdesk
Routing alerts into tickets with a priority, recipient and handling history. We agree which events go to the helpdesk, an administrator or your own team.ISO 27001 · TÜV NORD Polska
TÜV NORD Polska has certified Virtline’s information security management system to PN-EN ISO/IEC 27001:2023-08. The published certificate states its scope and validity.
View Virtline’s certificateMonitoring implementation process
We first select services for a pilot and agree how alerts will be handled. Coverage is expanded after measurements and notifications have been checked.
02
Selection and setup
We select the tool, data from devices and applications, and network measurement points. We check permissions, licensing, storage space, retention, standby components and connections to the helpdesk or system inventory.
03
Pilot and tests
We test agreed scenarios, such as a device outage, application delay, saturated link or failed backup. We check alert delivery and escalation; packet capture is tested only where it forms part of the scope.
04
Acceptance and reviews
We adjust thresholds, discuss results and hand over documentation. We agree review frequency, changes, updates and future extensions; ongoing operation requires a defined service scope.
Practical scope
What you receive
We hand over the configuration and information needed to operate monitoring. Acceptance results show what was checked and which matters remain open.
Monitored hosts, services and dependencies, with business priorities and responsible people. We identify the measurements included and the areas outside monitoring coverage.
Checks, thresholds, dashboards, notification channels and escalation paths. Maintenance windows and dependencies help reduce unnecessary alerts during planned work.
Results from controlled events, alert delivery and ticket routing. We record problems found, threshold adjustments and arrangements that still need verification.
Documentation and a configuration export, administrator access and review arrangements. Reports on availability, agreed service targets, response times and resource use support planning.
How much data does diagnosis need?
Some problems can be investigated using records of who communicates with whom and how much data is sent. Flowmon Collector gathers these records, including in NetFlow/IPFIX formats. Flowmon APM helps assess application response times. Where full packet analysis is needed, Flowmon Packet Investigator records and examines packets in PCAP format. We select measurements for the specific problem. We agree collection points, retention, storage and access because packets may contain sensitive information. Encryption limits visibility into packet contents. We agree data restriction or masking, and deletion. Bandwidth control, for example with Exinda Network Orchestrator, is a separate change requiring an assessment of the impact on services, a fallback arrangement and a rollback plan.
Questions about IT monitoring
Do you only implement Nagios?
+
No. We can implement Nagios or improve an existing setup, including custom service checks. We also consider Zabbix, PRTG, Grafana/Prometheus, Azure Monitor or a tool your business already uses. The choice depends on what needs checking, where data can be collected and who will operate the system. We discuss replacement and licence costs before implementation. For existing Cacti or System Center Operations Manager (SCOM) installations, we can agree a review of configuration, data sources and notifications.
Does backup monitoring include a restore test?
+
Monitoring can collect job statuses and restore-test results. Receiving a successful backup notification is not itself a data recovery test. We agree the test scope, responsible person and error reporting separately with the team managing backups.
Does IT monitoring replace SIEM or SOC?
+
No. Monitoring checks service availability and operating parameters. SIEM is a system for analysing related security events; a SOC is a team that handles them. We can agree how important alerts are forwarded and linked to system records or EDR endpoint protection. Infrastructure monitoring alone does not include these services or establish that NIS2 requirements have been met.
Does an alert mean the team responds around the clock?
+
Not automatically. The system can detect events and send alerts outside business hours, but 24/7 support, on-call cover, response times and repair scope must be agreed separately in the contract and supported by confirmed team availability. We also define your responsibilities and those of other providers.
Define your monitoring scope
Tell us about your critical services, current tools and recurring failures. Explain who should respond to alerts and during which hours. We will use this to discuss implementation and support scope.
Discuss IT monitoring