Operations | Monitoring | ITSM | DevOps | Cloud

A practical guide to React error monitoring

When designing effective error handling for React apps, the troubleshooting information you collect and display is critical. React errors can stem from a variety of causes, including user misconfiguration, backend and network issues, and mismatches in browser environments. Instrumenting your code to log critical context, including feature names, user data, and session activity, enables you to quickly identify where these errors originate.

Reproducing split brain on CloudNativePG

We run Postgres under an operator for automatic failover. That is a promise about what happens during a failure, so the only way to know you have it is to cause the failure and watch. The docs tell you what should happen. A config review tells you which knobs are set. Neither tells you how long an isolated primary keeps accepting writes after its replacement has been promoted, and that number decides whether a failover is clean or leaves you with two versions of your data.

Your AI Agents Can Take Action Now. Can You Prove They Should Have?

Enterprise AI agents clear every demo and pilot, then hit a compliance wall. The gap isn't technology—it's architecture. Discover why governance must sit inside the execution flow across six control points, not bolt on afterward as an afterthought at input and output only.

What Comes Next: Honeycomb Demos at O11yCon 2026

In this session at O11yCon, Purvi Kanal, Jamie Danielson, and Martin Holman demoed the new Canvas. Canvas now understands OpenTelemetry GenAI semantic conventions, and can show agent invocations, LLM calls, and tool calls all in one trace view. Humans and agents can work in the same place, with skills that let each team encode their own expertise so both the agent and their colleagues can use it. Multiplayer support means you can see your teammates' cursors and share charts.