Operations | Monitoring | ITSM | DevOps | Cloud

Figuring out why things break still sucks. We’ve got all the data: metrics, logs, traces, but getting to the actual root cause still takes way too long. Observability tools show us everything, but they don’t really tell us what’s wrong. So why do we even need to automate root cause analysis? First, time. Outages are expensive. And if your system has hundreds or thousands of services, digging through everything by hand just takes way too long.

We’ve added a new option to log in to Oh Dear: passkeys! When logging in using a passkey, you don’t have to type an email or password, and you won’t be redirect to a third party for logging in. It’s also super fast.

Ever feel like you’re flying blind in your AWS environment? You’re not alone. In the sprawling universe of microservices, containers, and serverless functions, trying to troubleshoot without proper observability is like trying to find a bug in a datacenter… with the lights off… while wearing sunglasses.

The HTTP Content-Security-Policy response header is used to control how the browser is allowed to load various content types. It is used to control which URLs, fonts, images, scripts, and more can be loaded onto the page. It’s a great defense against XSS (cross-site scripting), clickjacking, and cross-site vulnerabilities. The header can also specify a URL that will be used to send reports on violations of these properties.

Troubleshooting containerized applications can quickly become complex when logs are scattered across multiple systems. Most DevOps teams face this challenge daily—what starts as a simple container deployment often evolves into a complex logging puzzle. This guide explores Docker logging drivers in depth, covering configuration options, best practices, and practical solutions.