September 2021 Update: Routing voice calls to on-call staff
Yippie! Our September update adds live call routing as well as a voice mailbox with notification feature to SIGNL4. All details can be found in this article.
Yippie! Our September update adds live call routing as well as a voice mailbox with notification feature to SIGNL4. All details can be found in this article.
Our ecosystem continues to grow: we have added 10 new integrations within the last months. Integrations are the bridge between alert sources and on-call teams and have always been a top priority at iLert. They are one of the reasons why iLert is so easy to adopt for small and large companies alike.
The OnPage clinical communication and collaboration (CC&C) system is universally adopted by midwifery care communities across the United States and Canada. OnPage is proud to provide a real-time, secure collaboration platform that allows midwives to improve patient experience. This article examines the continued widespread adoption and implementation of OnPage’s industry-leading CC&C system by midwifery care communities.
If you’re a DevOps practitioner working in a Microsoft-centric environment, you’ll be pleased to learn that Logz.io recently added support for the popular Teams communications hub to help broadcast pressing alerts and other monitoring data. The integration comes on the heels of making the Logz.io platform directly available from within the Azure Console and expands organizations’ abilities to communicate and share notifications about everything from log data to security events.
In the SIGNL4 web portal you can manually export historic alert reports as.csv files. In some cases it might be useful to export alert data programmatically. For example you can forward all alerts including specific parameters to InfluxDB and show the alert history in Grafana to recognize peaks, trends and abnormalities over time. You can even use AIOps to recognize certain trends automatically. By using the SIGNL4 REST API it is possible to export alert data automatically.
What do IT security, production monitoring and technical field service have in common? In all scenarios there is need to notify the right people immediately in the event of technical malfunctions, urgent maintenance requests or emergencies to resolve the incident quickly and efficiently.
A few days ago I received an inquiry about a scripting problem from one of our longtime partners, to be exact our DCP Marc Handel from IT unlimited AG. In the exchange with Marc I realized that his idea to use the Enterprise Alert Scripting Host, the Windows Task Scheduler and CheckMK to realize a roundtrip monitoring could be interesting for the whole community. Especially for all our CheckMK customers.
Alerts are notifications from AIOps monitoring tools that indicate that there is an anomaly. IT teams get these alerts on their monitoring dashboard via emails or enterprise collaboration tools such as Slack or Teams. Service level agreements expect IT teams to analyze every alert within a specific timeframe and take appropriate action.
Alerts are indispensable to any IT operations system today. Site reliability engineers (SREs) or ITOps executives set up several monitoring tools for their IT landscape. When there is a change, high-risk action, or outage in any of these incidents, the monitoring tool triggers an automated alert. This could happen on the monitoring tool’s dashboard itself, via email, or enterprise collaboration tools like Slack or Teams.