Operations | Monitoring | ITSM | DevOps | Cloud

Comparing Firmware Development Environments - Linux, Windows, WSL2, and VMWare

About a year and a half ago, I decided to take a different approach to setting up a Zephyr environment for a new project at Intercreate. Instead of using my trusty VMWare Workstation Linux VM, I opted for WSL2. I was curious to find out: Would hardware pass-through for debugging work reliably? Would all of the tooling dependencies be supported? What about build system performance?

Launch Week Keynote: Log Management and Analytics

Logs have always been a critical component of observability, extending beyond embedded development. Many embedded teams rely heavily on logs and strive to enhance efficiency. Some struggle to extract value from their logs due to the complexities of collection and analysis. Regardless of your team's current situation, we are here to help. Our new Log Management and Analytics offering streamlines log collection, accelerates investigations, and transforms your logs into easily accessible insights across your entire fleet.

Debugging a Slack Integration with Sentry's Trace View

While building Sentry, we also use Sentry to identify bugs, performance slowdowns, and issues that worsen our users’ experience. With our focus on keeping developers in their flow as much as possible, that often means identifying, fixing, and improving our integrations with other critical developer tools. Recently, one of our customers reported an issue with our Slack integration that I was able to debug and resolve with the help of our Trace View.

Observability and Tracing: How to Improve Your Debugging Workflow

Having the right tools to support debugging is crucial for improving application performance and delivering an enhanced user experience. Traditional observability tools provide insights into application health and with a shift towards actionability, they also directly aid in the debuggability of your system, helping you pinpoint the root cause of issues in real-time.

Debugging INP With Honeycomb for Frontend Observability

Interaction to Next Paint is the newest of Google’s Core Web Vitals. The three metrics that make up the CWVs are Google’s attempt at defining proxy metrics for measuring things they believe are critical to a good user experience on the web. The three metrics are: Debugging and fixing these metrics can be quite complicated. In this post, I’m going to walk through how you can use Honeycomb for Frontend Observability to debug INP, which was just promoted to a stable Core Web Vital in March.

Why Clean Architecture makes debugging easier

Let’s start with things we already know - complex projects are inherently hard to debug. The more complicated they are, the harder it is to debug them. The size of the project naturally defines complexity’s lower bounds, but even the smallest projects can become unnecessarily complex and messy if you don’t pay attention to how you structure them. Though we can’t eliminate complexity, we can manage it effectively with the right approach.

How New IoT Security Regulations Will Shape the Industry's Future

New IoT security regulations are imminent, with businesses across the US, UK, and EU bracing for the impacts of the Cyber Resilience Act (CRA), Product Security Telecommunications Infrastructure, and Cyber Trust Mark. These are not just administrative changes; they represent a pivotal shift in how IoT devices will be developed, deployed, and managed. Ensuring security, privacy, and compliance is business-critical.

Debugging with Sentry and Expo

Sentry is a debuggability platform that provides real-time insights into production deployments with info to reproduce and fix errors, crashes, and slow code. We are very lucky to welcome Krystof Woldrich from Sentry to join the stream and live demo some debug magic. From the Expo side we will have debug wizard and father of Expo Atlas, Cedric Van Putten. The two of them are going to show a complete debug flow.