A continuously changing aircraft list is useful to inspect, but it is not something you want to watch all day. dump1090-alerts lets you describe the situations that matter and connect those conditions to a notification destination. The rules live in a TOML configuration you can read and review.
Conditions that remain understandable
The rule engine supports thirteen condition types and combines conditions within a rule. Cooldowns apply per rule and aircraft, which helps prevent the same ongoing situation from generating a notification on every poll. The first polling cycle establishes a baseline instead of treating every aircraft already present as a new arrival.
Choose where the result goes
Supported destinations include webhooks, ntfy, Discord, Telegram, email, and shell commands. This makes it possible to fit alerts into an existing workflow. Shell actions deserve particular care: configure only commands you intend to run, and test the rule against expected input before leaving it unattended.
Start small and tune
The implementation uses Python's standard library. Begin with a narrow rule and an easily inspected destination, then review what fires during normal receiver activity. Alerts describe the observations available to your station; missed coverage and stale upstream data still affect what a rule can detect.
Explore dump1090-alerts → · Source and documentation ↗