The Dashboard is the landing tab. It answers, at a glance:
is AIDE enabled ?
Is the baseline built ?When did it last run, when will it run next, and how many changes are waiting for review.
¶ Concept
File-integrity monitoring is only useful if it is running and current.
The Dashboard surfaces the two failure modes an operator must never miss: the baseline is missing, or events are piling up un-triaged.
A small bar chart breaks the open events down by severity.
¶ The header controls
- Run now — launch an integrity check (
aide --check) immediately, outside the schedule. Use it after maintenance to confirm the box is clean. - Reconfigure — regenerate
/etc/aide/aide.conffrom the current rule groups and re-apply the schedule. Run it after editing rules. - Enable / Disable Feature — the big status card. Enabling installs AIDE, seeds the rules and builds the first baseline; disabling stops the scheduled scans.
¶ The status fields
- Baseline Initialized — whether a trusted reference database exists. If not, no check can run; build it from the Baseline tab.
- Enabled — whether scheduled checks are active. The pencil opens the enable/disable action.
- Schedule — the current cadence (e.g. Daily / 03:30). The pencil opens the schedule editor (below).
- Last Run / Next Run — timing of the integrity scans.
- Un-Triaged Events — changes still waiting for a decision. Anything above zero needs attention in the Events tab.
- Highest severity — the worst open event (info → medium → high → critical).
¶ Editing the schedule
Click the pencil next to Schedule to open the scheduler. Pick a frequency (daily or weekly), the hour and minute, and — for weekly — the weekday. Save to write a managed cron entry (/etc/cron.d/artica-aide). Schedule integrity scans off-peak, and at least once a day; more often on exposed hosts.
