Services · Monitoring
Advanced monitoring of servers, services and players
Monitoring is the backbone of our service. We don’t stop at knowing whether a server is up: we watch every configuration item your clients’ experience depends on.
Metrics per service
Thresholds tuned to each service
Illustrative view
Visibility at every layer
Infrastructure
CPU, memory, storage, network and usage trends for every server.
Services and applications
Status and performance of every platform service: web servers, databases, queues, scheduled jobs, streaming and security certificates.
Players and stores
Connectivity and status of screens and audio players at every location.
From detection to prevention
Proactive, tiered alerts
Thresholds tuned to each service and automatic escalation, to act before the client notices.
Impact analysis
Because we know the dependencies between configuration items, we immediately see which services and clients each alert affects.
Capacity planning
Detailed history to anticipate when a network needs more resources.
Availability reports
Measurable evidence that service levels are met, ready to present to your clients.
Frequently asked questions
What's the difference between monitoring a server and monitoring a service?
A server can be up while an application on it is failing. Monitoring services catches the problems that basic monitoring misses.
Does monitoring cover air-gapped environments?
Yes. The local middleware monitors screens and players inside the isolated network and reports through the channels the client authorizes.
Let’s talk about your network and what you need to watch in it.