Operations | Monitoring | ITSM | DevOps | Cloud

Debugging a broken deployment can take hours, especially when the cause is unclear. Recently, a customer ran into this exact situation: their AI agent produced a Drupal site with broken composer scripts and mismatched database credentials, and nothing they tried got it running. This video shows how debugging works in practice on Upsun.

In a large-scale DevOps environment, small discrepancies lead to massive headaches. You’ve likely experienced it: a script runs perfectly on a developer’s laptop but fails in the production pipeline. You spend hours hunting for the cause, only to discover a mismatch in CLI versions. At JFrog, we know the JFrog CLI is vital to your automation, but managing it manually across thousands of users and pipelines is a hurdle that slows you down.

Here is a number worth sitting with: field engineers spend between 25 and 40% of their working day on tasks that have nothing to do with fixing anything. No diagnostics. No repairs. No customer uptime. Just sourcing part numbers, cross-referencing OEM manuals, translating customer-specific documentation, and waiting on help desks that are fielding the same questions they fielded last week.

For the world’s largest financial institutions, places like Citi and National Australia Bank, shipping code fast is just part of the job. But at that scale, speed is nothing without a rock-solid security foundation. It’s the non-negotiable starting point for every release. Most Harness users believe they are fully covered by our fine-grained Role-Based Access Control (RBAC) and Open Policy Agent (OPA).

Modern CI/CD platforms allow engineering teams to ship software faster than ever before. Pipelines complete in minutes. Deployments that once required carefully coordinated release windows now happen dozens of times per day. Platform engineering teams have succeeded in giving developers unprecedented autonomy, enabling them to build, test, and deploy their services with remarkable speed. Yet in highly regulated environments-especially in the financial services sector-speed alone cannot be the objective.

Netdata AI can already troubleshoot your alerts and generate Insights reports. What it couldn’t do, until now, was have a back-and-forth conversation. You could get a one-shot analysis, but you couldn’t ask follow-up questions, pull in additional context, or go from a quick question to a full investigation without starting over. We’ve added a conversational layer to Netdata AI.

Datadog Session Replay gives teams a video-like view of what real users experienced in their applications. Engineers rely on replays to connect errors and slowdowns to actual user behavior, while product managers use them to understand friction and improve critical flows. But finding the right replay and the right moment often means manually scanning long sessions without knowing whether they contain relevant signals.

Finding the right information across dashboards, monitors, and telemetry sources takes time, even for experienced engineers. When something breaks, it often means figuring out where to start, rebuilding queries, and jumping between metrics, logs, and traces before you can take action. The challenge isn’t a lack of data but the effort required to surface the right information at the right moment.

Being on call is an essential part of operating reliable distributed systems, but it comes with real human costs such as alert fatigue, sudden wakeups in the middle of the night, and the ongoing anxiety of what the next notification might bring. Many engineers know the feeling: Your phone lights up, a sound cuts through the silence, and your heart rate spikes before you’re even fully awake.