Operations | Monitoring | ITSM | DevOps | Cloud

You ask for a routine health check and expect a clean baseline. What came back was a pod that had restarted 788 times, unrelated to the question. AURA is connected to a Kubernetes cluster and to Prometheus through read-only MCP servers, running as one coordinator with two specialized workers. The prompt is one sentence: check the health of the cluster, and confirm whether all the pods are running. What comes back is not a baseline. AURA names the state as CrashLoopBackOff and attaches the restart count to it.

The platform shows you which service is failing and which paths it touches, and stops there. Point AURA at the same telemetry and the cause comes back too. Dash0 shows the product catalog service in a failed state across the selected window, with errors on the path from the frontend service.

This week's Feature Friday: Principal Product Manager Christine Byun walks through KPI cards, a new way to build custom dashboards in Engineering Intelligence. KPI cards pull key metrics, like change failure rate and rollback frequency, into compact tiles so they stay visible without taking up chart space. That means the metric you're actively working, incidents, in this demo, gets full-size room, without losing sight of the rest of your system.

NinjaOne Field CTO Jeff Hunter demonstrates capture & deploy a Windows Image using NinjaOne OS Deployment. In an elevated CMD terminal, run this command to sysprep: C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown Chapter Markers.

In this episode, Sean and Crystal explore the complex and rapidly evolving landscape of AI, data center impacts, regulation challenges, and societal implications. They discuss the urgency of establishing standards and the lessons from historical industrial revolutions to navigate AI's future responsibly.

Even small Oracle ASM issues can become big database problems. Here's how to spot the warning signs early. Tony and Tonie discuss how Redgate Monitor custom metrics help teams close a common monitoring gap: surfacing Oracle ASM health and performance issues before storage pressure, rebalancing problems, or disk group failures become database incidents.