Operations | Monitoring | ITSM | DevOps | Cloud

One of the things that struck me upon joining Honeycomb was the seemingly laissez-faire approach we took towards internal SLOs. From my own research (beginning with the classic SRE book, following Google’s example), I came to these conclusions: If you read the original SRE book when it was released, before the workbook came out, these conclusions all made sense.

Many people wonder what the difference is between monitoring vs. observability. While monitoring is simply watching a system, observability means truly understanding a system’s state. DevOps teams leverage observability to debug their applications or troubleshoot the root cause of system issues. Peak visibility is achieved by analyzing the three pillars of observability: Logs, metrics and traces.

In an era where there’s no shortage of established best practices and tools, engineering teams are consistently finding their ability to prevent, detect and resolve production issues is only getting harder. Why is this the case? Our most recent DevOps Pulse Survey highlighted alarming trends to this end.

At Kentik, we pride ourselves as innovators and thought-leaders for network observability. “Kentik is network observability” is more than a slogan for us. It’s an idea that informs our product roadmap and guides our problem-solving with customers. We’ve done a lot to explain network observability to prospects.

A few weeks back, I got the chance to sit down with our very own Jordan Perks from the Cribl Customer Success Team. Jordan is an Observability subject matter expert AND knows a thing or two about Cribl Products! After geeking out a bit about data best practices, we started chatting about enabling our customer champions to have different conversations with stakeholders across their organizations. When someone becomes an observability engineer, they step into a much different role.

In today's complex, multi-cloud environments, IT and engineering teams are under increasing pressure to respond to errors affecting their entire system. Therefore, IT operations, DevOps, and SRE teams are all striving to gain complete observability across these increasingly complex and diverse computing environments. But what exactly does observability mean?

The way businesses obtain infrastructure has changed dramatically over the past decade, as Infrastructure-as-a-Service (IaaS) has taken the place of self-hosted infrastructure for most IT deployments. At the same time, it has become common to build complex infrastructures that blend components from multiple providers – such as two or more public clouds (aka. multicloud infrastructure) or mixing an on-prem data center and a public cloud (aka. hybrid cloud infrastructure).

In the last few years, the usage of databases that charge by request, query, or insert—rather than by provisioned compute infrastructure (e.g., CPU, RAM, etc.)—has grown significantly. They’re popular for a lot of the same reasons that serverless compute functions are, as the cost will scale with your usage. No one is using your site? No problem: you’re not charged.

Today, during the ObservabilityCon 2022 keynote session, we announced a new open source project for frontend application observability, Grafana Faro. The project is launching with a highly configurable web SDK that instruments web applications to capture observability signals. This frontend telemetry can then be correlated with backend and infrastructure data for seamless, full-stack observability. There’s supposed to be a video here, but for some reason there isn’t.