JaneHQ::AlertRules
The condition and action vocabularies an alert group is built from. Kept here (not in the DB) because they are properties of the Jane agent's check families, not user data.
Constants
How many times an alert fires: once, or repeatedly at ALERT_FREQUENCIES.
Repeat interval, in minutes, when alert_count is "recurring".
What a new alert group starts with — the same default M/Monit uses.
The check families the agent emits (jane/src/utils/*.cr). event_for
maps a reported check name back to one of these.
Jane reports each check as "ok" or "alert", which are Succeeded and Failed here; "changed" is a transition between the two, so it is derived when a report lands rather than sent by the agent.
Class methods
Which event family a reported check name belongs to. Order matters: the File attribute checks ("File etc user") are suffixes of the plain existence check ("File etc").
The event a check name belongs to, as a label — shown as a hint beside each service in the form's Service picker.
Catalog order, unknown values dropped — how submitted picker values are normalized before they are stored.