Chronosphere

Tis' the season to be spooky. 🧛♂️

Ready to turn KubeCon conversations into real connections over a drink? Join us on Wednesday, Nov 12 (6–9pm ET) at the RT60 Rooftop Bar for our Cheers to Observability Happy Hour. Unwind, grab a drink, and connect with fellow engineers, SREs, and observability enthusiasts while taking in the Atlanta skyline. Expect great bites, craft cocktails, and even better company. Follow the guided observability trail to Cheers to Observability — the happiest hour at #KubeCon! RSVP 👉 https://bit.ly/3ISRqTn

Looking to tame your observability chaos? Lucky for you, we have a Chronosphere and Embrace webinar on October 28th, 1PM CST! What to expect: · How Chronosphere helps Observability Teams eliminate waste, prioritize the right signals, and keep cloud-native environments under control · Why Embrace’s mobile telemetry is a game-changer for bridging frontend-backend visibility gaps · How to align observability priorities for faster triage and stronger reliability · Frameworks to cut MTTR, manage costs, and build trust with engineering teams Register Now! 👉 https://bit.ly/4ok4TT1

Fluent Bit is an event-driven collector that turns near-real-time events into time-sensitive observability metrics when issues strike. It captures and distributes logs, metrics, and traces so teams: 🏃 Diagnose faster 🧑💻 Automate responses 🛣️ Route data to the right tools Read more: https://bit.ly/4gZPTXX

We hit the floor at SREcon 2025 in Dublin to ask: When you get back to your team, what’s the one thing you’ll actually share from the event? Here’s what they told us 👇

Big fall ahead for the Chronosphere team. After connecting with the open source community at All Things Open, we’re heading next to the Gartner IT Infrastructure, Operations & Cloud Strategies (IOCS) conferences in London and Las Vegas — continuing the conversation on what it really takes to operate reliably at scale. We’re proud to be recognized again in the Gartner® Magic Quadrant™ for Observability, validating what our customers already know: ✅ True visibility starts with control over your data. ✅ Efficiency isn’t about collecting more — it’s about extracting value. ✅ Open standards are the backbone of scalable observability. If you’re attending IOCS, stop by to see how we’re helping teams reduce observability waste, improve reliability, and deliver real business impact — with the data that matters most. 📍 London → Nov 17-18 📍 Las Vegas → Dec 9-11 👉 Let’s compare notes on how observability is evolving for the cloud-native era. #Chronosphere #GartnerIOCS #Observability #MagicQuadrant #CloudNative #SRE #PlatformEngineering

SLOs translate telemetry into a single, user-anchored reliability target so you can invest engineering time where it matters most. What changes when you adopt SLOs: ✅ Standardized SLIs (good/total) power clear burn-down charts and alerts tied to user impact. ✅ Error budgets quantify tradeoffs between feature velocity and reliability, ending subjective debates about “one more launch.” ✅ Policies kick in before the quarter is lost—freeze risky changes, prioritize reliability work, and automate rollbacks. ✅ User journeys lead. Tie SLOs to the experiences customers care about (availability, latency, freshness, durability), then decompose into component SLIs across your stack. ✅ Continuous improvement is baked in. Review weekly for course-corrections and quarterly for strategy—tighten/relax targets as you validate what truly moves user happiness.

We had a great time connecting with the open source community at All Things Open Conference this week! It was great to meet so many folks at the booth and swap ideas about observability and open source. A special shoutout to Katie Greenley and Eric D. Schabell, who led great conversations at unconference— thanks to everyone who joined and shared their insights! 📸 Check out a few of our favorite moments from the event below.

We recently asked what the state of your service-level-objectives is at your organization. The answer didn't surprise us! If you're struggling to get started with implementing SLOs, we have some tips for you. 1) Begin with the user, not the server 🧑💻 List the core user journeys (e.g., sign-in, checkout, search). Track what users feel: latency, error rate, availability—not CPU or memory. 2) Define the SLO (the promise) 🙏 Pick a realistic target per journey: e.g., 99.9% availability, p95 < 200 ms, 95% successful checkouts. 3) Choose your SLIs (the measurements) 📏 Examples: request duration, success/failure rate, availability over time. Don't have any data? Instrument now in your observability stack; even a basic counter + timer beats guessing. 4) Establish your error budget (the safety net) 💸 Your SLO is a contract; the error budget = how much unreliability you can “spend.” When you burn budget fast, pause feature velocity and fix reliability. 5) Alert on burn, not noise 🔕 Ditch metric spike pages. Use budget burn-rate alerts so you only wake up when users feel pain. Example: alert if 2-hour burn predicts breach within a day. 6) Start small, then scale ⚖️ Pick one or two critical journeys, get baseline, review weekly, and iterate. Avoid “microservices overload” at the start.Roll out SLOs gradually. 7) Make decisions with data 📊 Use SLO health to answer: Fix reliability or ship features? Socialize reports so product + eng stay aligned! 👉 TL;DR: User journeys → SLO target → SLI measure → error budget → burn-rate alerts → iterate. Start small, stay focused, and build trust with data that actually matters.

Fluent Bit fundamentals: everything starts with the event, and the plugins that make it useful. 👏 👏 👏 In v1.9+, metadata expands beyond just the Tag, alongside the other two core elements: Timestamp and Record (logs, metrics, traces). This primer sets up routing, processing, and extensibility you’ll use everywhere. 👉 Read the next article in the series: https://bit.ly/4mWQ7kj