Alerts

the alerts section in swimlane turbine provides visibility into alert notifications generated when playbook runs fail it complements the configuration of orchestration alerts by showing administrators the history of triggered alerts within a selected timeframe overview the alerts page displays a table of alerts, including alert – the type of alert generated time of alert – when the alert was triggered details – additional information about the failure or notification if no alerts are available for the selected time range, the table will display an empty state message “no alerts available for the selected time range ” time range filtering you can filter alerts by selecting a time window (for example, last 24 hours, last 7 days, or last 30 days) this allows administrators to focus on recent issues or review longer term trends in orchestration failures configuring orchestration alerts to enable and configure alerts in the admin panel , navigate to settings > tenant specific > orchestration alerts enable the send via email option by selecting the checkbox once enabled, a recipients field will appear here you can specify users – directly assign alerts to specific swimlane users groups – assign alerts to swimlane groups to ensure multiple team members are informed custom email ids – add external addresses if notifications need to go to recipients outside of swimlane administrators can add recipients by searching for swimlane users or groups, or by typing a new email address deactivated users or groups will not receive notifications when a playbook run fails, swimlane generates an email notification that contains a direct link to the failed playbook this allows administrators to quickly open the failed run and begin troubleshooting alert behavior immediate notifications – a failure triggers an alert email right away summary notifications – if another failure occurs within 30 minutes, instead of sending multiple emails, swimlane sends a single summary email this email contains a list of all failed playbook runs within that period, along with their corresponding playbook ids this approach ensures administrators stay informed without being overwhelmed by excessive notifications example email notification a typical orchestration alert email includes the playbook name and id the time of failure a direct link to the failed run in swimlane turbine clicking the link takes you directly to the corresponding playbook run, saving time in locating and diagnosing the issue benefits of orchestration alerts immediate awareness – administrators are informed as soon as failures occur actionable links – direct navigation to failed playbook runs speeds up investigation reduced noise – summary notifications prevent inbox flooding from repeated failures tenant specific configuration – alerts can be tailored for each tenant’s needs, ensuring relevance by enabling orchestration alerts, organizations can ensure quick response to failures, reduce downtime, and maintain high reliability of their automated workflows