Operations | Monitoring | ITSM | DevOps | Cloud

An account can show signs of disengagement long before a renewal conversation begins. Users may stop returning to a core workflow, stall during onboarding, or skip a newly released feature. Product teams often see these signals only at the user level, while annual recurring revenue (ARR), plan, renewal date, and ownership data remain in a customer relationship management (CRM) system or data warehouse.

Your error monitoring tool found a bug. Now what? For most teams, the answer is the same thing it has been for years: copy the stack trace, find the file, read the code, build a mental model of what went wrong, write the fix, write or update a test, push, and wait for CI. That process hasn’t changed much since error tracking became a category. The tools got better at telling you something broke. They never got better at fixing it.

We got a little behind on updating our changeLOG, so we’re dumping it all into this bLOG post instead. Think of it as one giant, retroactive changelog entry or, if you want to be dramatic about it, one massive prompt injection straight into your feed. Either way: here’s everything that shipped for Sentry Logs this summer. Would you rather listen to the team talk about what they built? Check out this video where Kyle and Josh talk about the latest updates on Logs.

Migrating your app to a new service can be scary. Render makes the deployment side easy, but a green deploy doesn’t mean everything is working. Silent failures are often the most dangerous kind. They go unnoticed until a customer calls to report a broken webhook or you realize the queue depth has been climbing since the cutover and nobody has caught it yet. The migrations that explode on deploy are not the ones you should fear. It’s those that look fine for three days.

The best SSL certificate monitoring tools are Hyperping (certificate checks inside a full uptime, on-call and status page workflow), TrackSSL (dedicated certificate inventory and change alerts), Xitoring (deepest published TLS analysis at the lowest price), UptimeRobot (largest free tier), Better Stack (certificate checks alongside logs, traces and incident response) and Oh Dear (whole-site health for agencies). I analyzed 26 tools and narrowed the list to these six.

Here's a scenario that will likely sound familiar: You’re building an executive overview dashboard that you would put on a wall-mounted screen so the whole room can see how the business is doing at a glance. It’s for a Shopify online store, and displays a mix of business and application signals, including latency panels, error-rate panels, and a big stat panel for revenue-per-week. It looked great. But something is missing.

For years, IT teams had a fairly contained job: keep the office network running. Every device, router, and switch that mattered was inside a building they controlled. That job doesn't exist anymore. Remote and hybrid work moved the "network" into hundreds of living rooms, home offices, and coffee shops, none of which IT can see, configure, or troubleshoot directly. So when a help desk ticket comes in saying "the app is slow" or "my calls keep dropping," IT is left guessing. Is it the company's network?