Loading video...

Video Failed to Load

Go Home

Observability on Cloudflare just got better! Create visualizations from natural language – "show me my cache hit rate". Within a chart you can also click a spike and investigate what happened much easier. Also really enjoying our animated quick start dialogs for products :) 5 new things in total:...

15,202 views • 6 days ago •via X (Twitter)

14 Comments

sunil pai's profile picture
sunil pai2 days ago

um this needs a lot more attention

Daniel Lockyer's profile picture
Daniel Lockyer6 days ago

hello

Brayden's profile picture
Brayden6 days ago

hi

Nipsuli's profile picture
Nipsuli6 days ago

Nice! Was missing this the other day

Doug Standley's profile picture
Doug Standley5 days ago

.@Cloudflare I see you and you are killin’ it! Bravo!

Tornike Sirbiladze's profile picture
Tornike Sirbiladze3 days ago

Can you inspect and edit the SQL behind a generated chart? That would make the natural-language starting point much more useful for repeat investigations.

Alek's profile picture
Alek6 days ago

Brayden - which spike made cache-hit debugging fastest?

❀ Sofie p.'s profile picture
❀ Sofie p.4 days ago

Couldn't agree more

René Cannaò's profile picture
René Cannaò6 days ago

Does the investigation link preserve the exact time window and filters? Being able to send a colleague the same view of a spike is very useful during an incident. A dashboard that opens on "last 15 minutes" can tell a different story by the time they click it.

Daniel Priscu's profile picture
Daniel Priscu6 days ago

clicking straight into a spike will save more time than the text-to-chart part

Raxit Majithiya's profile picture
Raxit Majithiya2 days ago

👀 Custom alerts on observability data

Coffee Cat's profile picture
Coffee Cat2 days ago

自然语言画图省的是上手成本,可观测性真正的瓶颈是数据量和采样成本:全量 trace 存下来,账单涨得比流量快。建议错误全留、成功按比例采,再用 trace id 反查——前提是 id 一路透传不断链。

Arjun Maniyani's profile picture
Arjun Maniyani2 days ago

There's no way generative UI has become this good. I'm seriously impressed

seridarivus 🇷🇴's profile picture
seridarivus 🇷🇴6 days ago

NL → chart is fine until "cache hit rate" silently means edge vs origin and nobody notices the wrong series. Does the prompt log which metric ID it actually picked?

Related Videos

Today, we're making Error Tracking by Better Stack generally available. Sentry-compatible. AI-native. At 1/6th the price. Here's why we built it, and how to get the most out of it. What's wrong with error tracking today? Most teams use Sentry. It's solid! But at scale, the bills get brutal. Just 100M exceptions with 90 day lookback? ~$30,000 on Sentry. We charge ~$5,000 for the exact same thing. The math isn't subtle. And so most teams still end up sampling. Which means missing the exact exception that caused the outage. The bigger problem: errors are orphaned data. Your exception lands in Sentry. Your logs are in Datadog. Your traces are somewhere else. Root cause analysis becomes a multi-tab archaeology project at 3 am. We built error tracking natively inside Better Stack: the same platform where your logs, traces, metrics, uptime checks, and on-call schedules already live. Errors are just another signal. They belong together. The part that changes how your team works: Our AI SRE doesn't just surface errors. It fixes them. See a new exception? One click. The AI SRE analyzes the full context, from stack traces, environment variables, browser sessions, related logs and recent deploys, and opens a pull request. Not a ticket. Not a summary. A pull request with the fix. This is what happens when error tracking is fully integrated with the rest of your observability stack instead of bolted on separately. The AI has everything it needs to actually act. The migration is trivial: 1. Keep your existing Sentry SDK. Don't touch a single line of instrumentation code. 2. Point the DSN at Better Stack. 3. Done. Errors flow in. Your dashboards work. Your alerts work. 4. New exception appears. Click "Fix with AI SRE." Pull request lands in your repo. 5. Review, merge, close. That's the whole workflow. The AI angle is real, not a marketing badge. LLMs are genuinely good at fixing bugs if they have full context. The reason AI coding assistants sometimes frustrate engineers is incomplete information, not the model. We solve that by giving the AI SRE your entire telemetry stack as context. Stack traces, logs, traces, service maps, previous incidents and much more. All of it, in one place, at the moment it matters. Observability tools are only useful if you actually ingest all your data. At current prices of other tools, most teams can't afford to. Now you can, and your AI SRE can actually do something about it.

Juraj Masar

15,134 views • 6 months ago