Many organizations today are dealing today a lot of complexity and disconnected tools. Teams and departments are running in parallel but siloed from each other. People are burned out from a lot of manual work, and everyone is crunched for time. This is not a happy ecosystem to live in. If this digital ecosystem doesn’t work together, your teams don’t know what’s going on and they lack the right information.
If you aren’t frightened enough this Halloween, spend some time reading these tales of glitchy horror! Then, save your company from becoming a ghost story with Anodot’s anomaly detection and keep your platforms running smoothly.
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 telecom industry has always seemed to navigate well through tech changes. As the industry has evolved, it’s managed to transform from landline to mobile carriers, then from voice calls to messaging and data-centric networks. In many developed markets telcos are creating ecosystems for the data-driven economy. The next frontier is shaping up to be one driven by machine learning (ML) and artificial intelligence (AI).
I’m going to assume most people who read this blog are familiar with PagerDuty. But just in case anyone isn’t, PagerDuty is a tool we use in IT to notify us if some predefined check has failed. Maybe a key process has died or maybe we’re not seeing our expected traffic volume or maybe our server has stopped responding to ping. Whatever it is, PagerDuty will relentlessly, remorselessly, and loudly notify whoever is on call that something needs attention.
Software teams seeking to provide better products and services must focus on faster release cycles. But running reliable systems at ever-increasing speeds presents a big challenge. Software teams can have both quality and speed by adjusting the policies around ongoing service ownership. While on-call plays a large part in this model, advancement in knowledge, more resilient code, increased collaboration, and practice also mean engineers don’t have to wake up to a nightmare.
