A guide to active alert categories and notification boundaries. Alerts are intended to surface meaningful changes in supported measurements without turning missing, stale or uncertain data into a false emergency signal.
Every alert is bound to a specific signal and source
GeoLira alerts are built on defined metrics or events rather than a generic activity label. Custom thresholds include Kp, IMF Bz, solar-wind speed and Schumann relative activity with approved source_id and station_id bindings. Events such as CME and flares use separate event catalogs.
Threshold, profile, cooldown and quiet hours have different roles
A sensitivity profile proposes threshold values, a custom threshold defines the actual condition, cooldown limits repeated notifications and quiet hours control delivery timing. Time-dependent delivery settings require a configured timezone. These settings do not alter the source data; they only control how the user wants to be notified.
A notification is not a prediction of personal effect
Crossing a threshold means only that an explicit rule for that metric became true. It does not establish the cause of a feeling, act as medical advice or guarantee a local aurora or storm. When a source is too old or invalid, an alert that requires current evidence should fail closed instead of using the last number without warning.