Operations | Monitoring | ITSM | DevOps | Cloud

Every developer knows the moment: CI goes red, and you face a choice. Open the browser and click through the web UI to the run, the workflow, the job, the step, the log line. Or stay in the terminal, where the fix is going to happen anyway. The new CircleCI CLI exists so you can stay. It’s 1.0, it’s in beta, and it’s a ground-up rewrite in Go, not an iteration on the CLI we’ve shipped for years.

Your monitoring stack never sleeps. Datadog fires a spike, ServiceNow spins up a ticket, your RMM flags a failed backup, and every one of those signals competes for attention across email, dashboards, and chat channels. For IT Ops teams running on-call rotations, the volume itself becomes the problem. Alert fatigue sets in, critical notifications blend into the noise, and the one incident that matters at 3 a.m. gets buried under a hundred that don’t. The cost is real.

One of the primary reasons organizations adopt Grafana Cloud is to create a single pane of glass across the data they collect from self-hosted systems, cloud providers, and third-party platforms. Bringing those signals together enables richer correlations, reduces tool sprawl, and makes it easier for teams to understand what's happening across their environment. But as observability grows and becomes more centralized, access management becomes more important.

A platform is an environment that allows software to run smoothly across the infrastructure, runtime, and application layers. The key word there is “smoothly”: a good platform connects those layers so well that you don’t notice it. That’s what Ubuntu Server has become: the essential layer between bare metal and the apps running on top, continuously optimized across resource management, networking, and security. Ubuntu 26.04 LTS represents over 12 years of that work coming together.

The Puppet Observability Data Connector is a premium Forge module included with Puppet Enterprise Advanced (PEA). This module provides a deeper dive into your Puppet agent reports. Visualizing these metrics gives you a great way to identify what is healthy and unhealthy in your environment.

There is a question a lot of engineering leaders are quietly sitting with right now: we have rolled out AI tools across the team, the developers seem faster, so why isn't more software actually shipping? It is a reasonable thing to consider. Pull requests are opening faster. Lines of code per sprint are up. The boilerplate that used to take full afternoons now takes minutes. By every local measure, the investment is paying off.

This is Post 2 of The Governance Gap series. Post 1, "The New Software Creator," established that the most significant shift from AI isn't developer speed - it's that the population of builders has fundamentally expanded. Something quiet happened in most engineering organizations over the last 18 months.

A digital transformation can help a business thrive. Developing a strong technology stack that works for your business is essential for growth. Investing in a digital transformation means finding what works for your business and ensuring the best operations through your digital tools.

DASH 2026 brought thousands of engineers, builders, security professionals, and technology leaders to New York City for 2½ days focused on building, operating, and securing modern systems. Across hands-on sessions and more than 40 customer talks, teams shared how they’re tackling real-world challenges at scale with Datadog. On stage, the keynote set the direction for what’s next across observability, security, and AI, highlighting a shift toward more autonomous, AI-assisted operations.

Not all alerts are created equal. Some are resolved quickly by the on-call engineer. Others signal something serious enough to affect your business and require your whole team to coordinate. That is why we redesigned incidents as a dedicated coordination workspace for the alerts that have the most business impact.‍ Until now, incidents in ilert were used to communicate status updates to customers and stakeholders. Creating one meant publishing to your status page. We have separated the two.