Operations | Monitoring | ITSM | DevOps | Cloud

It is 2 AM. Someone on-call gets paged. Conversion rates on the checkout page dropped 30 percent in the last hour. The immediate questions are familiar. Is this a JavaScript error? A slow API call? A broken third-party script? A performance regression that never throws an exception but quietly drives users away? In most teams, answering those questions is not hard because the data is missing. It is hard because the investigation is split across too many places.

The Zephyr west tool is a powerful workspace manager, but it is admittedly pretty feature-rich: there’s a lot of functionality buried inside that tool! I thought it would be interesting to share a few tips and tricks that I use with west to make my Zephyr development workflow a little smoother.

We’ve been quietly solving a problem that most teams haven’t hit yet, but they’re about to. SSL certificate lifetimes are dropping to 47 days. If you’re managing certificates manually today, you have a very short window before that becomes a real operational problem. We know, because it happened to us first.

The most frustrating sentence in modern engineering is no longer "it works on my machine." It is: "It worked in the playground." When an LLM-powered feature, such as a RAG-based search, an autonomous agent, or a dynamic prompt engine, fails in production, it doesn’t throw a standard stack trace. It returns "slop," hallucinations, or silent retrieval failures. Standard debugging workflows fail during triage because LLM hallucinations cannot be reproduced using static mocks or clean seed data.

Let’s suppose you’re building an even smarter fishtank. You’re adding temperature and salinity sensors, logging timestamped readings to flash. The struct is your binary record format – every field at a fixed byte offset, so you can read it back on any system that knows the layout. You use fixed-width types from stdint.h and pack(1) to strip out compiler-inserted padding. This is the advice I had always received and given, and it’s correct – as far as it goes.

While it has taken longer than some people expected, Matter is finally going mainstream. Brands including Ikea, Kwikset, and Bosch have shipped matter devices, and matter hubs can increasingly be found in people’s homes. Many dev kits out there are matter compatible, and if you want to build a simple application you can find good example code and get started quickly. This is fine if your use case fits neatly within existing Matter clusters, but direct internet communication is not straightforward.

Production bugs that only reproduce in actual traffic can be some of the most frustrating bugs in software development. You can stare at your logs, add traces to your code, add instrumentation – and still not be able to see the actual requests that went over the wire. And that gets even harder when the requests are encrypted and the system is a black box. You can use tools like Wireshark or Kubeshark to capture the requests.