Operations | Monitoring | ITSM | DevOps | Cloud

Most cloud cost dashboards are built for one audience. The finance team wants to see totals by department. The engineering team wants to see costs by service. The DevOps team wants to see environment-level breakdowns. When everyone looks at the same dashboard, nobody gets what they actually need. This is where tailored cloud cost visibility starts to matter. When a team can see its own costs clearly, it moves faster, takes ownership, and starts treating cost data like it actually matters.

The expectations placed on infrastructure leaders have shifted in a way that is subtle on the surface but significant in practice, and much of that shift comes down to infrastructure cost visibility. Reliability and performance still matter, but they are no longer the differentiators they once were. Most enterprise environments are stable by design, and uptime is assumed. What has changed is the level of scrutiny around cost and decision-making.

When we launched AppSignal MCP in beta, OAuth was on the roadmap but not yet shipped. We were issuing static bearer tokens — enough to connect Claude Desktop, Cursor, and Windsurf, but not the one-click install path in the MCP Registry, and not GitHub Copilot's recommended setup. That's fixed.

IncidentHub tracked 48000 SaaS and Cloud outages in 2025. The average organization depends on 100+ SaaS apps, making third-party vendor monitoring a crucial aspect of risk management and business continuity for almost all modern organizations. Better SaaS outage alerting is about monitoring the right parts of your third-party services, and routing alerts to the right people at the right time.

CFEngine 3.24.4+, 3.27.1+, and 3.28.0+ include a change to how findfiles() handles trailing slashes on directory paths. This change restores trailing slashes to directory results, but with improved consistency compared to earlier versions. The new behavior ensures that directory paths always include a trailing slash, making them reliably distinguishable from file paths regardless of the glob pattern used.

There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure, control, recovery, and communication. When us-east-1 goes wrong, the problem is not only that workloads fail.

Teams are shipping more code, faster than ever, as they increasingly automate their processes with CI/CD and AI. But high-velocity pull-request workflows and large monorepos, where many PRs are merged continuously, are feeling the pain as they grow: pull requests race to merge before the branch changes again, “green” builds still break due to semantic merge conflicts, and developers are stuck babysitting merges instead of building features.