Monitoring and alerts

Device health, checks and thresholds by policy, script and server checks, quiet monitoring and onboarding findings, maintenance and planned states, the alert list, what raised an alert and fixing it, alert types and their noise figures, storms and one cause one alert, flapping, found and ignored items, and turning alerts into tickets and emails.

1 How monitoring works What the agent collects, how policies decide what each device checks and when it alerts, and where monitoring shows up in Tenvara.
2 Device health Read the fleet Health page, a device's health, charts, checks and services, and find out why a device is monitored the way it is.
3 Policies, checks and thresholds Create monitoring policies for customers, sites, groups and devices, start from templates by server role, add checks and set alert thresholds.
4 Maintenance windows and mutes Hold alerts back during patching nights and planned work with maintenance windows and maintenance mode, mark things as test, unused or retired with a planned state, or mute one noisy rule on one device, without losing anything.
5 Alerts Work the alert list across every source, group it, read an alert with the chart around when it fired, and take, snooze, acknowledge, resolve with how it ended or add it to a ticket.
6 Alerts into tickets and notifications Use alert rules to decide which alerts open tickets and who is emailed, send alert digests, and choose how alerts reach you.
7 Quiet monitoring and onboarding findings How Tenvara stays quiet about normal things, handles offline devices, checks that only fit some machines and checks that could not run, and turns a new customer's first scans into one report.
8 Script, file and server checks Monitor anything with a script check, watch files, folders and installed software, check websites and VPNs from Tenvara itself, and find what is filling a disk.
9 Alert history, dependencies and flapping See a device's alert history with time to acknowledge and resolve, hold back alerts behind a firewall, switch or host that is down, and stop alerts that keep opening and clearing from paging anyone.
10 What raised an alert, and fixing it from the alert Read Raised by on any alert to see the exact record behind it, run the fix its module offers with a preview first, and choose which alert types offer, suggest or run their fix by themselves.
11 Alert types See every kind of alert Tenvara can raise with its noise over 30 days, turn a type or a whole group off or on, overall or for one customer, with an end date and a reason, undo an automatic lowering, and choose whether each type makes tickets.
12 Alert storms and first-run findings How an alert storm starts, what it holds back and when it ends, how alerts with one cause become one alert, and how the first run of a new check, a module, an import or a first sync becomes one findings report instead of a flood of alerts.
13 Found, adopted and ignored What Tenvara finds by itself, how adopting works, and how to ignore something for good with a reason, see everything ignored with who, when and why, and bring it back.
14 How Tenvara decides what reaches someone The checks every alert and detection passes before anyone is told: a short wait, your own work, planned states and maintenance, one cause one alert, learning periods, and what Critical means.
15 How did it end? Closing alerts and the noise figures The five outcomes every close asks for, what reopens and what stays closed within 7 days, the 30-day noise figures on Alert types and security rules, automatic lowering with Undo, and the weekly noisiest five.