Operations | Monitoring | ITSM | DevOps | Cloud

It's a story as old as the web itself: someone on your team gets excited to install a new tool. The tool promises to finally give you a clear view into the problems your users have with your product. Your team agrees to give it a go. The errors start coming... ...and they don't stop coming... Soon enough, most of your team has either created an email filter to manage all the alerts, or has unsubscribed themselves entirely. Just like all the other tools. Welcome to alert fatigue.

On-call is a special working hour arrangement under employment law. It comes into effect when the employee is obliged to be contactable at least by phone, so they can start work in an emergency. On-call duty is generally counted as time specifically meant for work purposes. In practice, this means that employees are normally not allowed to work while on-call. However, there may be exceptions. For example, on-call employees may also work from home if they can be reached through their work device.

Amazon Web Services (AWS) offers 100+ services, each focusing on a specific area of functionality. However, it can be challenging to pick the right services for the task and also to provision them. AWS Elastic Beanstalk, lets you easily deploy and manage applications without the need to learn about the underlying infrastructure that runs these applications.

With BigPanda’s self-service Email Parser, extracting alert data from emails has never been more simple. In our latest video in the Fast track series, we explore the benefits of this tool. This parser is ideal for monitoring tools and systems that do not support REST API and or rely solely on email to generate and send alerts. So no matter what tools your organization utilizes, this feature can help you turn all of those alert emails into actionable incidents within BigPanda’s platform.

We have released another update for Enterprise Alert 9 (version 9.4) which enhances the cloud bridge and MS Teams integrations. This will help you to setup scenarios where you wish to active your Enterprise Alert remote actions from with the Signl4 app as well as allowing for using a proxy to configure the MS Teams integration. Read all details in this article.

The MIM Expo (Major Incident Management) always delivers, and this year’s recent gathering was no exception. At this annual event, we always get a unique opportunity to hear about what’s top of mind with major incidents and SRE professionals from all the world.

Sometimes an IT ticket is just an IT ticket. But far more often, when one or a few tickets are submitted, it means there are many more users and systems exposed to the same issue. IT issues can quickly get out of control and affect many employees, sometimes overnight. When these get out of control, they can become “top call drivers” that bring your team, department, business lines, and even entire business to a halt.

Sentry Alerts ping you on Slack, Microsoft Teams, or Pager Duty when something goes needs your attention. However, too many alerts can turn your notification channel into an endless noise feed. I spoke with dozens of Sentry customers in the past 6 months, and something I heard over and over again was “Sentry can get noisy at times” and “There are days I can’t keep up with Sentry notifications because we get so many of them”. Does this sound familiar?

Microsoft Teams is a popular integration request for our Alerting feature, and the Raygun team is busy at work making this feature available to all our customers. We will be notifying all our customers when this feature is available. You are also welcome to keep an eye out for the launch announcement in our Changelog. Since it’s such a popular integration request, we thought we’d share some specs and screenshots with you as we progress through the work.