POKOMONITOR · SELF-HOSTED MONITORING
PokoMonitor brings device health, site status, infrastructure metrics, services, and custom checks into one view. It is built for retail and distributed organisations, and works equally well at a single site when clear, self-hosted monitoring is required.
MONITORING FOR REAL OPERATIONS
In a distributed organisation, a fault rarely remains a purely technical event. An unavailable POS terminal slows sales, an unreachable network path interrupts data exchange, and a stopped service can halt an important local process. When those signals live in separate tools, the team loses time establishing where the problem is and how urgent it is.
PokoMonitor groups devices by site and optional region, rolls each site status up from its device estate, and surfaces what needs action. IT teams get the detail required for diagnosis, while operations users can follow a shared overview without entering administration screens.
A DEFINING POKOMONITOR ADVANTAGE
Site Map turns a long device list into a clear geographic view of operations. Healthy sites remain quiet, while warning, critical, or stale status immediately identifies the location that needs investigation. The team can filter by region, open a specific site, and continue down to the device or check that changed its status.
See immediately which city, region, or site has a problem.
Regional filtering helps each responsible team focus on the sites that matter to them.
Move from a marker to the site, its devices, alerts, and the specific failed checks.
A TOUR THROUGH THE PRODUCT
The map provides geographic context, while the other views guide the team through priority, site, device, check, and alert.
The home dashboard presents the overall health verdict, device and site totals, active alerts, and a concrete list of exceptions. Instead of searching through tables, the team immediately sees the site, device, and reason behind the changed status.
Site cards show rolled-up status, region, address, and device count. Search, filters, and priority sorting let the team keep healthy locations in the background and open the site with a critical, warning, or stale signal first.
The device view connects hostname, site, last report, and current CPU, RAM, and disk values. Alerts retain severity, trigger time, message, and acknowledgement state. The team can distinguish an active fault, a transient spike, a stale device, and an event already owned by a colleague.
WHAT YOU CAN MONITOR
Checks can apply globally, to one site, or to a specific device. Each has its own interval, severity, consecutive-failure threshold, and expected result.
CPU, RAM, disk, network throughput, uptime, and last report time across current and historical views.
Check a named process, Windows service, or Linux systemd unit on the device.
Ping, TCP ports, HTTP URLs, Linux mount points, and Windows UNC or SMB paths.
Run a local script or executable and verify its expected exit code.
ALERTING WITHOUT UNNECESSARY NOISE
Rules for resources, unavailable devices, and failed checks can require sustained duration or multiple consecutive failures before raising an alert.
Notifications are delivered through your SMTP server or a JSON webhook. Rules can use different channels and optional recovery messages.
Schedule maintenance for a site, device, or individual check, or temporarily silence a rule without losing history.
Open alerts can be acknowledged, searched, and filtered. Recovery is recorded so each event has a clear beginning and end.
HOW IT WORKS
The server, PostgreSQL database, web interface, and agents run in your infrastructure. Monitoring does not depend on a POKO ITS cloud service, and the signed licence is validated locally. Users connect over the internal network or your VPN, in line with your organisation security architecture.
FROM INSTALLATION TO OPERATIONAL VIEW
PokoMonitor is deployed in the agreed server environment as a Windows service or Linux systemd service, with its database, HTTPS access, and backup plan.
Regions, sites, addresses, time zones, and device roles are defined.
The agent is installed as a Windows Service or Linux systemd service and receives its own durable credential.
Thresholds, services, processes, network paths, URLs, and notification channels are configured.
The team validates failure scenarios, maintenance, recovery, dashboards, and operational ownership.
DEMO AND LICENSING
The planned demo currently covers up to 15 active devices for 30 days, with a built-in grace period. The device count and final terms are confirmed for each request because the demo policy may change.
Demo support includes a product walkthrough, installation and implementation help, and best-practice guidance.
NO-OBLIGATION CONVERSATION
Describe the objective and current state. We will explain what is worth checking and what a realistic first step could look like.
