DHCP, DNS, NTP, and RADIUS
Checks for a client wireless network, AP management network, site, user context, or SSID context.
Integration-ready Operations
Evidence becomes part of the workflow.
Control brings technical results into the systems where teams prioritize, assign, and track work. APIs, webhooks, and reporting handoffs connect service checks, findings, and root-cause context with existing operational processes.
API-driven checks
Run targeted checks. Process structured results.
The API can trigger checks for a defined scope and return machine-readable results.
PoE, speed, duplex, and counters
Validate every AP in a building or individual Ethernet interfaces and switch ports.
Onboarding and reachability
Site Engine onboarding, policy context, cloud communication, and the effects of firewall rules or SSL inspection.
Events and handoff
Not merely an alert. A case with context.
- Status and severity
- Site, building, AP, client, SSID, and VLAN
- executed checks and runtimes
- technical evidence and root-cause correlation
- affected infrastructure and recommended action
- link to the report or investigation
ITSM and automation
Connect to established workflows.
API- and webhook-based integration points connect Control to ServiceNow, Jira Service Management, Zendesk, Freshservice, Matrix42, or custom workflow and monitoring systems.
Example flow
From a DNS failure to an actionable incident.
- Monitor detects that a RADIUS hostname cannot be resolved through a site's DNS resolver.
- Control evaluates scope and severity.
- An API or webhook event passes the site, resolver, target, error message, and evidence.
- The ITSM platform creates or updates the appropriate incident.
- The responsible team receives a clear technical starting point.