Event and alert filtering matters because alert fatigue is one of the most crucial issues in alerting and alert management. SIGNL4 implements a lightweight and effective way of filtering events. The overall process is based on alert categories. Alert categories are applied using a keyword search across the entire payload of incoming third-party events. But
Handover procedures in operations and maintenance are a key element of business continuity. As work in this field is usually organized in shifts, it is essential to keep track of any critical incidents, machine breakdowns, job ownership, completion, issues that are still open or unresolved and other related items. Such knowledge has a significant impact
If you are still handing over a shared on-call duty phone or pager (sometimes called ‘operations phone’), it is time to rethink your process. The Covid19-induced new normal has a dramatic impact on our work live and social behavior. We work from home and that is especially true for the IT workforce. We meet with
A new article in the September issue of German magazine LANLine (“Automation creates productivity”) summarizes typical challenges and problems in network monitoring very well and is worth reading. I would like to briefly discuss some of the problems addressed and how our product SIGNL4 was developed as a solution for exactly these problems. Problem 1:
SIGNL4 provides great support for geolocation information and in multiple ways. When a new alert with geolocation information is displayed in the mobile app, the app renders a map to visualize geographic information of the incident. A double click allows to open the default map application on the mobile device, e.g. to get directions or
“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. First layer of alert routing – duty status SIGNL4 currently provides
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. Using Teams and Slack as additional notification channels By default,
Event and alert severity are extremely 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. However, as monitoring, security and other control systems have different ways
We are more than excited to host our first ‘ask me anything’ session on SIGNL4. Here is our agenda: You will meet our experts Matt, René and Patrick. Any questions or feature requests can be discussed and answered here. We will give you an update on the latest features additions Get exclusive insights into our
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. New webhook payload format The SIGNL4 webhook now also digest payload of ‘application/x-www-form-urlencoded‘ type. A payload/webhook call of this kind would like: POST /webhook/ihdm29y8