Operations | Monitoring | ITSM | DevOps | Cloud

Debugging

What Data Should be Monitored From Bluetooth Devices in the Field?

Building a Bluetooth-enabled IoT device? Here’s a pro tip: monitor what you can’t see. Blecon’s Simon Ford explains how hidden issues—like high retry rates in Bluetooth communication—may not trigger alerts but can reveal critical insights about your device’s true performance.

Learn how to use the enhanced related items tab in Rollbar to speed up debugging.

The Related Tab is a helpful tool that shows you other items related to the one you’re looking at. This makes it easier to see if the same issue is happening in different parts of your code base or if there are similar items that might be connected. Knowing this can help you understand if a problem is widespread or if there are other occurrences that could help you debug it quicker.

WSL2 for Firmware Development

This guide provides instructions for setting up an environment for developing, debugging, and programming embedded systems firmware in the Windows Subsystem for Linux (WSL2). WSL2 provides a convenient and stable Linux development environment for working on embedded systems firmware. If you’re curious about toolchain performance, check out this comparison of firmware development environments, but the summary is that WSL2 is about 2x the speed of Windows and similar to “bare metal” Linux.

Capacity Management: Debugging Exceeded Rate Limits

Snuba, the primary storage and query service for event data that powers Sentry in production, has historically been doing rate limiting under the hood, making it hard to discover and increasing time to resolve customer support requests. This is not something you’d know the specifics of unless you were deep in the Snuba code. But as we triage support questions from customers, one issue tends to pop up: RateLimitExceeded. You got tired of not getting query results.