“Servcies&Systems” category subscriptions provide a highly flexible way of routing alerts to specific user groups. This can for instance be used to route alerts based on responsibilities or skills. But other scenarios are possible too as the category subscription mechanism is extremely powerful. SIGNL4 currently provides two fundamental ways of routing alerts. The first layer is the routing of alerts based on the “on duty” status.
SIGNL4 provides plug-and-play chatbot integrations with Microsoft Teams and Slack, both via certified chatbot apps. Why does it makes sense to integrate SIGNL4 with chat tools after all? There are two basic uses cases that we address with the integration into Teams and Slack. By default, SIGNL4 notifies by mobile push, text and voicecalls, all according to user preference. The focus is clearly on mobile alert notifications. And of course, tracking and escalation of critical alerts is built-in.
Our first SIGNL4 release tin 2020 includes some great new features. Have a look. For all those who still need to work with pager devices in addition to their smartphone, it is now possible to include this device in the alarm workflow. This might be the case to secure alert delivery even in areas with poor cell coverage. Legcy pager support is provided through a new app we have added to the SIGNL4 app gallery. This apps sends an email to a paging gateway.
Event and alert severity are extremly important information for an effective alert management and response. Severity information determine the speed of response, needed resource allocation and the action path taken. Naturally, critical alerts have higher priority than major alerts which again overrule minor alerts.
Our 2nd December update adds alert counters to the web app, allows for disabling the opt-in/out from “Services & Systems” categories and adds a new encoding format to the SIGNL4 webbhook.
Our December update includes a new role model for users in a SIGNL4 team, great new app features and integration with Azure Sentinel. Two default user roles are now available in each SIGNL4 team: Administrator and User. This allows for restricting standard user rights versus administrative access. For existing teams, all users are migrated to administrators, i.e. you should check this role assignment and downgrade some team members to users yourself if necessary.
Have you ever wanted to get important alerts from Azure Monitor notified on your smartphone and have all the important details of the problem at your fingertips? Have you ever missed the option to easily change the status of alerts from Azure Monitor in the Azure smartphone app? Ever missed a push notification because there was no persistent and advanced alerting? Then this article is for you.
This article describes how SIGNL4 can be generally authorized as an enterprise app for Azure AD users (Marketplace Link). This is important if you want to implement the use of SIGNL4 in your company with existing user accounts from the Azure AD.
The October update of the mobile app includes the improvements described below and the user experience includes a new feature. The user interface of the app has been improved so that you can now decide for yourself if you want to see all Signls on the dashboard differentiated by categories. Using the “More” button on the dashboard’s Signl widget, you can now open a context menu and show or hide the display of the categories.
Our September update improves the assignment of categories to Signl alerts, hence the enrichment and routing of alerts to the right people. Until now, a ‘Services & Systems’ category was assigned to a Signl alert, if at least one of the entered keywords was found in the event content or text delivered to SIGNL4 by email or webhook. This basically represents a logical ‘OR’ operator for this keywords search.
