v1.15.0

Added

• Custom notifications: you can now create your own notifications from the server settings in the mobile apps. Each notification has a name, an optional description, and can be enabled, disabled, edited, or deleted at any time. Disabled notifications are kept but stop firing; deleted ones are removed permanently.
• Flexible trigger conditions: decide exactly when a notification fires by combining simple rules such as the scenario, the country, the target, or the IP owner (for example: scenario is SSH brute-force and country is Spain). You can also trigger on repeated activity, such as 3 matching alerts within 10 seconds, or skip conditions entirely to fire on any alerts within a time window.
• Custom message: write the text that will be sent every time your notification triggers.
• Delivery channels: configure how notifications reach you from the server settings, via ntfy or email, and choose one or more channels for each notification. Every channel can be tested with a test message before saving it, and channels that are in use cannot be deleted by mistake.
• Cooldown for notifications: right after a notification is sent, matching alerts that arrive within the cooldown time are ignored, so a busy period sends fewer, calmer notifications. You can pick the cooldown when creating or editing a notification, with options from 10 seconds up to 5 minutes, and one minute is used by default.
• Sent history: the API keeps a history of the notifications it has sent so you can review them from the mobile apps.
• Trace notifications back to their alerts: every sent notification remembers which alerts triggered it, and you can now open the full list of those alerts with their details from the sent-notification history.
• Alert details in your notifications: when creating or editing a notification, you can now turn on "Include alert information". Every notification will then carry the details of the alerts that triggered it, right in the message body. You stay in control of where those details go: only delivery channels that support rich alert details will include them, while the rest keep receiving your plain message. The app shows you which of your channels support it, and the option explains this as you set it up.

Changed

• Setting up notification channels is now guided by the server: the mobile apps build each provider form automatically, grouping fields into sections and only showing the fields that apply to what you have already filled in.
• Channel passwords and tokens are now handled more safely. They are accepted when you save a channel but are never returned afterwards, so they can no longer be seen by anyone reading the channel configuration. Editing a channel keeps its saved secrets unless you explicitly change or remove them.
• Notification conditions accept an empty filter group, which simply matches every alert. Combined with the repeated-matches option, this lets you fire on any number of alerts within a time window without picking any filter.
• Alert details in notifications are now easier to read: the summary and alert tables have a light gray border around every cell, and each event table is clearly separated from the next one instead of appearing as one dense block.

Fixed

• Repeated alerts no longer send a flood of notifications. If you set up a notification for something like "3 matching alerts in 10 seconds", a burst of 5 alerts used to send the same notification several times. Now each burst sends one notification.

Notes

• The new notification and channel screens, as well as the cooldown picker, require updated mobile apps. Older app versions keep working as before but will not show the new screens.
• Alert details are included when the notification is delivered through an email channel. Other channels will support them in future releases.
• If you have been using the beta versions, this stable release includes everything from v1.15.0-beta.1 to v1.15.0-beta.5. No manual action is needed: just update the API and keep your current settings.