-
Gains and Losses: Is Observability a No-Brainer?
Observability: it’s a buzzword, but is it worth the hype? Many organizations haven’t yet embraced it, and this post explores the potential gains and losses associated with implementing Observability, as well as the significant risks of not implementing it. The Costs of Observability: What You Stand to Lose Let’s be realistic, Observability isn’t free. There…
-
The power of context: No Observability without connected data
When it comes to troubleshooting and ensuring system health, Observability is all about one essential concept: connecting the dots. To identify and resolve problems effectively, we need to understand what happened, where it happened, and when it happened—all in context. This requires more than just collecting data; it demands that data be connected in meaningful…
-
Meet The Ducktor: Your Observability Troubleshooting Ally 🦆💡
When it comes to observability, the road to clarity can sometimes feel like navigating a maze of metrics, logs, and traces. That’s where The Ducktor comes in – a unique blend of problem-solving expertise and rubberducking magic, brought to life by Rainer Schuppe. The concept of rubberducking is simple: explain your problem out loud, often…
-
Troubleshooting 101: How observability helps you fix issues faster
When it comes to managing modern IT systems, troubleshooting is one of the most critical activities. It’s about identifying and resolving issues that slow down applications, disrupt services, and ultimately cost time, money, and customer trust. A well-established troubleshooting process, supported by robust observability practices, can make all the difference in diagnosing and fixing problems…
-
Whack-a-Mole for Pros
In my 30 years in IT I have seen many things – good ones and bad ones. The bad ones usually had to do with the performance of systems or rather the lack of it. And a few of them stuck in my mind and will come back to the surface time and time again…
-
Performance Monitoring is easy
Finding out if your application or your system is performing well is no rocket science. It is actually really easy -because: There are only 2 conditions – Slow or Failed.It is too slow or it doesn’t work at all and throws an error in the face of the user. Or – superbingo – it is…
New South Wales, Australia
info@example.com
987-065-40321
10 AM – 5 PM, Australiaa
troubleshooting
Archive
Categorise
Recent Posts
- The Unsung Heroes: Why OpenTelemetry’s Semantic Conventions are another Game-Changer
- Beyond the walls: Understanding and overcoming Observability vendor lock-in
- Observability Data: Where Do We Put All This Stuff?
- Gains and Losses: Is Observability a No-Brainer?
- The power of context: No Observability without connected data
Tags
Archaeology Automation Basics business Context convention Data demo DevOps Field flexibility General Grafana Information Instrumentation Introduction Jaeger Logs metrics Mindset Monitoring O11y Observability OpenSearch opentelemetry operations Otel Overhead platform engineering Practice RCA Responsibility Semantic conventions SRE standard storage strategy Summer Training troubleshooting vendor
