Operations | Monitoring | ITSM | DevOps | Cloud

The world of IT has gone through a significant amount of change in the last five to 10 years, and the rate of digital transformation can be challenging for organizations of all sizes. Keeping up with new and evolving capabilities alongside an increasingly distributed talent pool can be tough. That’s why it has always been my goal to keep up with the latest trends and provide the best tools for professionals working in the IT trenches. One of those emerging trends is observability.

Google’s Core Web Vitals (CWVs) are used to rank the performance of mobile sites or pages. It’s easy to see when your CWV scores are low, but it’s not always clear exactly why that’s happening. In Honeycomb’s new guide, Tracking Core Web Vitals with Honeycomb and Vercel, you can learn how to capture, analyze, and debug your real-world CWV performance using a free Honeycomb account.

How much does monitoring and observability actually cost us? We all collect logs, metrics, traces, and possibly other telemetry data. Yet, this can get expensive pretty quickly, especially in today’s microservices-based systems.

Wherever you read about observability, you are told that there are "3 pillars" of observability - Metrics, Traces and Logs. An image that is generally projected is something like this. But wait a minute, why are there only three pillars, and does it really matter to the end user? At the end of the day, users are just trying to solve their problems fast.

In this article, I’m going to walk you through adding attributes to your spans in.NET that contain information about the code that generated the span. We’ll also look at ways to do this automatically using a library I’ve created.

As more companies adopt SaaS services over on-premise delivery models, there is a natural concern around data security and platform availability. Words on a vendor’s website can provide insights to prospective customers on the process and policies that companies have in place to alleviate these concerns. However, the old adage of “actions speak louder than words” does apply. Trust in a website’s words only goes so far.

“Lead time to deploy” means the interval from when the code gets written to when it’s been deployed to production. It has also been described as “how long it takes you to run CI/CD.” How important is it? It’s nigh-on impossible to have a high-performing team if you have a long lead time, and shortening your lead time makes your team perform better, both directly and indirectly.

My organization doesn’t want me spending time on instrumenting my product. What can I do? Thanks for the question! You’ll be relieved to hear that you’re in the majority, and also that there are quick (and easy) steps you can do to prove that instrumenting your code is worthwhile.