Operations | Monitoring | ITSM | DevOps | Cloud

Distributed tracing has been growing in popularity as a primary tool for investigating performance issues in microservices systems. Our recent DevOps Pulse survey shows a 38% increase year-over-year in organizations’ tracing use. Furthermore, 64% of those respondents who are not yet using tracing indicated plans to adopt it in the next two years. However, many organizations have yet to realize just how much potential distributed tracing holds.

With Microsoft Teams usage continuing to increase, it was only a matter of time until we also saw the rise of Teams voice through PSTN. Even though this requires more expensive Microsoft 365 licenses, the return on investment can be significant purely based on the pricing structure but sizable savings can be realized when it comes to management overhead costs. However, it can be a challenge to ensure PSTN call quality for all your business lines and users.

Error-free apps are envied by all software teams today. But building and maintaining such an app is not as easy as it looks. You need to constantly keep a check on your app to see when it faces exceptions or errors. This is why we have so many error tracking tools in the current market. Rollbar is a popular error monitoring tool used for tracking and fixing all types of bugs and errors in modern applications. However, it has shortcomings too.

A developers perspective is different. While managing various sectors in a software, sometimes it would be difficult to monitor the activities and identify the bug that is disrupting the functions. What if you can spot the error beforehand, and resolve it at the earliest? The strategies that we focus on, and implement are the ones that help us effectively manage our tasks. That is possible by knowing about Observability. Let's learn in detail about it through this blog. TABLE OF CONTENTS.

In the real world, when we implement systems, there are often many kinds of users, such as super business users and some level 1 support technicians who understand the application domain and can support a lot of your applications. Still, due to limited skills and experience with Azure, they are constrained to how much of the application they can help. A great example of this is when you have a solution that uses Azure Service Bus.

Welcome to the Cloud 66 Changelog. These are the changes that have gone out this month.

We're a small team of engineers right now, but each engineer has experience working at companies who invested heavily in observability. While we can't afford months of time dedicated to our tooling, we want to come as close as possible to what we know is good, while running as little as we can- ideally buying, not building. Even with these constraints, we've been surprised at just how good we've managed to get our setup.

When you read the phrase “employee experience” (or even just good-old “user experience”), what comes to mind? One of the first things most of us think about, at least in an IT setting, is probably a system’s user interface. How hard or easy is the software to use? How intuitive is it? How appealing is its design? These are important considerations, but a good experience requires more than a good interface.

The rolling Comcast outage on Monday, November 8th and Tuesday, November 9th affected customers across the U.S., knocking users offline around the country. The first wave took place Monday evening in the San Francisco Bay area. The second, which had a wider geographic impact, occurred Tuesday morning, primarily affecting broad swathes of the Midwest, Southeast, and East Coast.

Observability is a measure of how well the internal state of a system can be inferred from its external outputs. It helps us understand what is happening in our application and troubleshoot problems when they arise. It’s an essential part of running production workloads and providing a reliable service that attracts and retains satisfied customers.