Operations | Monitoring | ITSM | DevOps | Cloud

From Observability for GenAI Applications (Grafana OpenTelemetry Community Call)

It's all about balance ¯\_(ツ)_/¯

Cut down on noisy telemetry data and move toward high signal density.

In this demo, Product Manager David Cavuto walks through how Cribl Notebooks helps security and IT teams investigate faster by combining live data, historical context, and interactive analysis — all in one place.

Take an in-depth tour of the Uptime.com RUM report. Comprehensively understand your users – and your baselines. Organize RUM data by URL(s) or group URL(s) to track subdomains; segment data by devices, operating systems, browsers, countries, other geographies – to compare metrics within specific time windows to your website or application’s performance monitoring baselines.

In the January edition of the Kubernetes Monitoring Helm chart office hours, we discuss the version 3.7 release, the upcoming 3.7 and 4.0 releases and features, and we discuss the upcoming deprecation of the 1.x and 2.0 versions.

Most governance models focus on what happens before production. Approvals. Tickets. Change records. But software delivery doesn’t end at deploy. Runtime is where change management is validated. It’s where systems prove whether controls actually work and where risk becomes real. If governance stops at deployment, you’re not managing change. You’re managing intent. In this video, Mike Long (CEO & Co-founder, Kosli) explains why runtime is the true source of control, why approvals alone don’t reduce risk, and how modern teams build governance that reflects reality, not paperwork.

AI is moving fast, and it’s tempting to believe it can automate software governance end to end. But compliance and security aren’t probabilistic problems. They don’t accept “close enough.” They don’t accept summaries. They can’t tolerate hallucinations. Governance depends on facts. Irrefutable, provable evidence of how systems actually changed.

If you're spinning up a whole container just for one test, you’re doing it wrong. Old way: Full DB container + pg_restore New way: speedscale + proxymock It records actual DB traffic and mocks it "on the wire." Test smarter, not harder.

Self-service has been around forever. So why are tickets still piling up? Because portals do not resolve issues. They push work to employees, then escalate anyway. Watch Zero Ticket Minute. Autonomous resolution is next.