Operations | Monitoring | ITSM | DevOps | Cloud

Debugging

Pocket article: How to implement and use `.noinit` RAM

Imagine there’s an embedded system that needs to persist some state when the processor restarts (either intentionally or due to a catastrophic error). This could be some external hardware information (what’s the position of a motor or actuator?) or a method to communicate the reset to the user (display some information on the device’s display). A simple way to store information through a reboot is to use what’s called“non-initialized” memory.

Datadog acquires Ozcode

At Datadog, we believe that having visibility into production is crucial to building better software, especially as modern environments become more and more complex. Bugs that occur in production are often difficult to reproduce locally, which leaves developers guessing about what went wrong. To solve this problem, teams need the same depth of visibility into their production environments as they do into their local environments.

New Events and Jobs Pages on Interrupt

François, Chris, and I started Interrupt 2.5 years ago because we wanted a repository of great embedded firmware content, which didn’t exist. Looking back at all the posts that our community contributors have published, we think we’ve made a respectable attempt at this goal. Our goals for Interrupt were always more ambitious than just a blog with quality content. We wanted Interrupt to become a hub for everything related to embedded firmware.

How to Debug, Update & Monitor Embedded Android Devices

Even when you think there are no bugs in your fleet of Android OS devices, huge issues can come up at any time. How do you find and fix those issues before your customers notice them? With full device observability, you'll never have to worry about even the most high-impact bugs affecting your IoT devices in development or production.

Automatically format and lint code with pre-commit

I love clean and tidy codebases. I love them even more if I don’t have to manually spend hours doing it myself. The problem is not everyone shares the same love and passion for tidy codebases, especially when we’re pressed for time trying to get a new firmware build released. This is where automated formatting and linting tools come in.

Announcing Workflows - Fix k8s issues on the fly

Meet "Workflow" from Komodor, the feature that automates troubleshooting common errors in Kubernetes. Leveraging Komodor’s change intelligence capabilities, Workflow's smart algorithm automatically detects Kubernetes issues and responds with a series of checks that quickly pinpoint its root cause. Not stopping there, Komodor uses the information to provide made-to-measure instruction for remediation, turning troubleshooting into a fast and effortless experience for dev and ops.