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
Sometimes you need to query an existing mailbox for specific emails instead of forwarding emails directly to your SIGNL4 team email address. This example uses Zapier to query a Gmail mail account. New emails with specific content then trigger alert notifications through SIGNL4. Zapier is great workflow tool and provides integrations with almost any mailbox type.
Machines, pumps, valves, fire alert systems, temperature sensors, smoke detectors, etc. often do not offer IT integration. Instead, they provide simple analog cables to interface with dry contacts. Monitoring these I/O states and detecting abnormal behavior or malfunctions a common scenario in industrial IoT. Operations teams in charge of business and operational continuity need to know
In a previous article we’ve shown how to send alerts to SIGNL4 from Amazon Alexa. It is also possible to do the same using the Google Assistant, either on your mobile device or using your Google Home speaker. Setting it up is easy if you are tech-savvy. You need an Android phone with the Google Assistant,
SIGNL4 offers easy-to-use interfaces for triggering notifications, e.g. email and Webhook. In some scenarios you might want to send signals manually from a Web portal. Google Forms is one option to add this feature to SIGNL4. The following steps show you how to setup a simple Web form for manually sending signals to your SIGNL4
SIGNL4 offers a powerful API to extend functionality and to embed it seamlessly into other applications and services. Using the API you can for instance build custom ‘who is on duty’ dashboards or trigger actions in case an alert has been acknowledged in the SIGNL4 mobile app. You can also build a web page to
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
We live in a somewhat paradoxical world. Our cars, or those that will soon be automatically brought to us via an Alexa voice command, drive us e. g. independently to the doctor or in front of a furniture store. Once there, however, it is just not possible to read in the chip card for registration
Managers and executives are always interested in current company data and KPIs (“key performance indicators”). This includes information about the current monthly and annual turnover. But also promising customer requests (A leads) that may require the collaboration of several departments. And of course also critical technical incidents at customers who need a quick solution to ensure
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