The update of December 2018 adds great features for enriching Signls with additional information (‘alert enrichment’). With “Services and Systems” categories, SIGNL4 already comes with an unique approach of categorizing alerts through colouring and acoustics, i.e. a dedicated push sound. But why not use this categorization feature for adding information to Signl alerts? Why is
Alarms in your SIGNL4 team can also be created manually from a Slack conversation. This is basically quite simple and consists of the following digital assets: a custom Slack App for SIGNL4, which you create in your own Slack-Team the Slack EventsAPI (https://api.slack.com/events-api). This API forwards desired messages/information from Slack to a remote HTTP endpoint
If you are using AWS CloudWatch for monitoring your AWS assets 24/7, an effective routing of alarms to IT personnel during after-business-hours is essential for a swift handling of any problems and incidents occurring any given time of the day. This post explains how to route AWS CloudWatch alarms with SIGNL4 to improve your after hour incident response while using
Nowadays most IT admins will get an email if their website monitoring solution detects a health issue or a website down. Maybe your entire team gets an email. But how likely are you to check your inbox every minute. And don’t you want share on-call duty across your team members? You simply don’t want to have everybody
Are you using Azure Application Insights for health monitoring of your website or web app? If so, I bet you have alerts setup to get notified in case of service health issues. By default, you or your whole team will get an email. But how do you know who took ownership. And in case of urgent issues, how do
SIGNL4 provides a convenient, out-of-the-box solution to send mobile SCOM alerts to your ops teams. With SIGNL4 you can build subject expert teams and send SCOM alerts to team members on duty. With the SIGNL4 mobile app, teams easily check-in and check-out to receive SCOM alerts when they are on call. The mobile app will
Microsoft Flow is a great intuitive workflow and process automation app. It provides a simplified graphic workflow orchestration approach. One of the most used actions in flows is sending or forwarding notifications upon events in your business process. Common notification channels email and mobile push through the Microsoft’ Notification connector. If you need to notify your team and
With SIGNL4, ServiceNow is complemented with intelligent mobile alert notifications for IT ops teams. Alerts will be routed to the right person who is on call/on duty. Team members will be notified persistently until acknowledgement. Incident ownership can be seen and tracked throughout the team. This significantly accelerates the response to critical incidents that need swift attention
Responding to OMS alerts occuring in after-hours can be challenging with Microsoft’s native mobile app, because: People forget to turn off notifications when their duty has ended, but getting them when you are off duty sucks There is no know way for the team to know if people on duty responded to alerts Push sounds are inappropriate for reliable
SIGNL4 provides persistent and real-time alert notifications to your admin team. Sending alert notifications exclusively to members on duty reduces response times, notification noise and fatigue. Ownership of alerts improves accountability and ensures real-time transparency. Sample Use Case We will setup an operational alert for an Azure Database. The alert condition will be based on the total