Documentation / Modules
Monitoring & topology
Agent and agentless monitoring with dependency-aware suppression, so one switch reboot is one ticket rather than fourteen alerts.
What is monitored
- Agents on endpoints and servers
- SNMP for switches, firewalls, UPS, printers and anything else that speaks it
- Synthetic checks — HTTP, TCP, DNS, certificate expiry
- Database performance
- Cloud and tenant state
Thresholds and baselines
Static thresholds where they make sense, and per-asset baselines where they do not. A server that always runs at 80% memory is not an incident every night.
Where there is not enough history to establish a baseline, the platform says so rather than inventing one from a default.
Correlation and suppression
Alerts are correlated to their cause using topology. A switch reboot that produces fourteen alerts across nine devices becomes one ticket with thirteen suppressed against it.
Suppressed alerts are listed under the ticket, never deleted. A suppression you cannot inspect is a suppression you cannot trust.
Device support
SNMP profiles cover the common device classes. Where a device is not recognised, Genie proposes a profile from a walk — reading the OIDs, proposing meanings, units and plausible ranges.
A proposed profile collects nothing and alarms on nothing until a person confirms it. A wrong profile silently in production produces confidently wrong monitoring, which is worse than none.
Flapping
A target that oscillates is detected as flapping and reported as such, rather than generating an alert per transition. The flap itself is the finding.
Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.
Thirty days · read-only · no card
Run it beside what you already have, against your real clients. It tells you what your tools are reporting that is not true.