Notifications¶
Info
Notifications about ticket updates are available from LogMan.io v25.30.
LogMan.io Alerts can send notifications about ticket activity through several channels and delivery modes.
Configuration is stored in the Library at /Alerts/Notifications/settings.yaml.
Channels
Delivery modes
- Scheduled — sent at configured intervals
- Instant — sent immediately when an event occurs
- SLA — sent when an SLA is violated
Configuration¶
Note
Notifications are sent through the ASAB Iris microservice. Ensure it is properly configured before enabling notifications.
Enable Notifications¶
To enable a notification channel, add the corresponding section to the LMIO Alerts configuration in /Site/model.yaml.
services:
lmio-alerts:
asab:
config:
notification:email: {} # Enable email notifications
notification:push: {} # Enable push notifications
notification:slack: {} # Enable Slack notifications
notification:sms: {} # Enable SMS notifications
Instant Notifications¶
An instant notification is sent immediately, regardless of any scheduling settings.
Instant notifications are sent when a new ticket is created.
Enable Instant Notifications¶
---
define:
type: alerts/notifications
email:
instant: {}
Template and Wrapper¶
To use a template or wrapper other than the defaults, add a params section for the notification type:
---
define:
type: alerts/notifications
email:
instant:
params:
template: /Templates/Email/Test.md
wrapper: /Templates/Wrapper/Simple Wrapper.html
Advanced Settings¶
To filter notifications by a ticket parameter, add an exclude section.
Use the standard comparison operators gt / gte / lt / lte / eq.
Note
Only the ticket's base parameters are supported. Ticket attributes are not currently supported.
---
define:
type: alerts/notifications
email:
instant:
exclude:
# Do not send notifications for tickets with severity lowest
- attribute: severity
op: eq
value: lowest
Scheduled Notifications¶
Notification Period¶
The default notification period is 1 hour.
The period can be configured per notification type in model.yaml (duration values such as 2h).
Send Slack Notifications Every Two Hours
services:
lmio-alerts:
asab:
config:
notification:slack:
period: 2h
Pause Scheduled Notifications¶
Notifications can be paused at the tenant level and per notification type. During a pause, updates are either discarded or delayed.
Note
Default Library settings for notifications:
- Notifications are sent only during standard working hours (06:00–16:00 UTC)
- Notifications are paused from Friday 16:00 UTC until Monday 06:00 UTC
- Accumulated updates are sent to email and Slack when notifications resume after a pause
- Accumulated updates are not sent by SMS when notifications resume after a pause
Adjust the default settings if required.
Notification Type Schedule
---
define:
type: alerts/notifications
slack: # (1)
schedule:
- at: 0 16 * * FRI # (2)
duration: 42h # (3)
action: discard # (4)
# Send accumulated updates
- at: 0 16 * * * # (5)
duration: 14h # (6)
action: delay # (7)
- Notification type (for example,
slack,email, orsms) - Stop sending notifications every Friday at 16:00 UTC (standard cron expression)
- Pause notifications for 42 hours; resume Monday at 06:00 UTC
- Do not send accumulated updates when notifications resume
- Stop sending notifications every day at 16:00 UTC
- Pause notifications for 14 hours; resume at 06:00 UTC
- Send accumulated updates when notifications resume
Supported duration suffixes:
- Y: year (365 days)
- M: month (31 days)
- W: week
- D: day
- h: hour
- m: minute
Examples: 3h (three hours), 5M (five months), 1Y (one year).
Mute Scheduled Notifications¶
No scheduled notifications are sent for a muted ticket, even when the ticket is updated.
To mute or unmute scheduled notifications, use the bell icon in the ticket details.
Email Notifications¶
Default generic values for the to (recipient) and from (sender) parameters can be configured in model.yaml.
services:
lmio-alerts:
asab:
config:
notification:email:
from: tester@teskalabs.com
to: user@teskalabs.com
The from parameter is optional.
To send notifications to one or more default destination addresses, configure the to parameter. Multiple addresses can be configured by separating them with commas, e.g. user1@teskalabs.com,user2@teskalabs.com.
- Ticket has a responder, and
tois configured → notifications are sent to both the responder and the configured default address(es) - Ticket has a responder, and
tois not configured → notifications are sent to the responder only - Ticket has no responder, and
tois configured → notifications are sent to the configured default address(es) - Ticket has no responder, and
tois not configured → notifications are not sent
Email: Ticket Created¶
Sent when a ticket is created (instant notification).
Hint
If needed, enable or edit the Library template Ticket Created.md at /Templates/Email/.
Email: Scheduled¶
Ticket update data is sent at the configured intervals.
Hint
If needed, enable or edit the Library template Ticket Updated.md at /Templates/Email/.
Email: Responder Assigned¶
The responder is notified when assigned to a ticket.
Hint
If needed, enable or edit the Library template Ticket Assignment.md at /Templates/Email/.
Email: SLA¶
Sent when an SLA violation is detected.
Hint
If needed, enable or edit the Library template SLA.md at /Templates/Email/.
Push Notifications¶
Hint
For scheduled notifications, enable or edit the Library template Ticket Updated.md at /Templates/Push/ if needed.
Slack Notifications¶
If a tenant-specific token and channel are available for asab-iris, notifications are delivered to the designated channel.
Hint
For scheduled notifications, enable or edit the Library template Ticket Updated.md at /Templates/Slack/ if needed.
SMS Notifications¶
The default phone number can be configured in model.yaml.
services:
lmio-alerts:
asab:
config:
notification:sms:
phone: 700700700 # default phone number
Warning
In LogMan.io v25.30, multiple phone numbers in SMS notifications are not supported. The configured phone number is used for notifications across all tenants.
- Ticket has a responder, and default
phoneis configured → notifications are sent to the responder - Ticket has a responder, and default
phoneis not configured → notifications are sent to the responder - Ticket has no responder, and default
phoneis configured → notifications are sent to the default phone number - Ticket has no responder, and default
phoneis not configured → notifications are not sent
Responders should have their phone number specified in their credentials profile.
Hint
For scheduled notifications, enable or edit the Library template Ticket Updated.md at /Templates/SMS/ if needed.