Operations | Monitoring | ITSM | DevOps | Cloud

We’ve rolled out a small improvement to Status Embed and Status Modal that gives you more flexibility in how you integrate status information into your site. With this update, you can now choose between JavaScript and iFrame embeds.

Modern infrastructure is no longer just about what you build and run internally. Most DevOps and system administration teams rely on a growing number of external SaaS services, including cloud providers, monitoring tools, authentication systems, CI/CD platforms, communication tools, and more. When one of these services fails, your application may still look healthy internally, while users are already experiencing issues.

If you work in game development, VFX, or any industry dealing with large binary assets, chances are your codebase lives in Perforce P4. It’s the version control system behind some of the biggest games and creative projects in the world — and until now, it’s been one of the last major SCMs without first-class Sentry support. Today, we’re changing that. The Sentry + Perforce P4 integration is now generally available for all Sentry organizations.

Two commands. That’s how little it takes to go from nothing to a fully configured Sentry project with error monitoring, performance tracing, and session replay: Click to Copy No signup form. No email verification dance. No dashboard tab-switching to copy-paste a DSN into your.env. Your account is created, your project is provisioned, and five environment variables land in your working directory, ready for your SDK to pick up. And if you’re using a coding agent?

At Atlassian, we use Merge Queues to ship frequent changes with confidence and streamline pull request merges. Across some of our busiest codebases, Merge Queues have sharply reduced incident frequency and turned merging from a stressful bottleneck into a background task. Today, most of our largest repositories rely on Merge Queues—over 70 large repos across products like Jira, Rovo, Trello, and others—having safely landed 30,000 pull requests since adopting Merge Queues Beta last quarter.

Modern IT operations aren’t short on tools. Monitoring tools. Ticketing systems. Alerting platforms. Documentation repositories. Dashboards. Scripts. Runbooks. And yet, when something breaks, the workflow still looks strangely familiar: Somewhere along the way you’re asking yourself: Is the problem even here? This is the everyday friction of IT operations. Not the big outages. Its the constant small mysteries that take far longer to solve than they should.

Across the IT industry, AI is being positioned as the next evolution of operations. But for many IT teams, AI still feels disconnected from the tools they rely on every day. Dashboards get smarter. Reports get faster. But workflows stay the same. Stuck in vendor silos or a CLI, IT teams have been looking for ways to bolt AI into workflows, but what often comes out is a Frankenstein-like web of APIs and MCP hosts. AI is meant to make life easier for IT teams – not make it more difficult.