Operations | Monitoring | ITSM | DevOps | Cloud

A lot of talk around OpenTelemetry has to do with instrumentation, especially auto-instrumentation, about OTel being vendor neutral, being open and a defacto standard. But how you use the final output of OTel is what makes business difference. In other words, how do you use it to make your life as an SRE/DevOps/biz person easier? How do you have to set things up to truly solve production issues faster?

With all the discussion in the dev community lately about changes made at Heroku, we wanted to use this moment to talk about PaaS (Platform as a Service) providers and how AppSignal can be a vital tool to ensure you're using your app's hosts for everything from optimal performance to lower usage bills.

Modern data centres are hitting a wall that faster CPUs alone cannot fix. As workloads scale out and latency budgets shrink, the impact of moving data between servers is starting to become the most significant factor in overall performance. Remote Direct Memory Access, or RDMA, is one of the technologies reshaping how that data moves, and it forces a rethink of some long-held assumptions in data centre networking. This article is the first in a short series.

ilert now supports a native WhaTap integration, connecting AI-native observability with AI-first incident management in a seamless workflow. This integration allows DevOps, SRE, and IT teams to move instantly from detection to resolution – cutting through alert noise, improving coordination, and dramatically reducing MTTR in even the most complex IT environments.

If you’re using AWS Bedrock, AWS can use your data for model improvement by default. VPC endpoints do not prevent this. You need to explicitly opt out inside AWS Organizations. It takes 2 minutes, and in this blog I’ll show you how.

As codebases grow across many different services, it becomes harder to see what test suites actually cover. AI-assisted development and faster release cycles increase the volume of changes landing in repositories, raising the risk that untested code will make it through to production. To maintain a high standard, teams need clear and scalable visibility across repositories, consistent testing standards, and a way to catch blind spots before they reach users.

Moving quickly is essential for modern engineering teams, but speed without guardrails can introduce hidden risks in testing. As organizations scale, teams often define and apply coverage standards inconsistently across services and repositories. What qualifies as “acceptable coverage” in one project may be completely different in another. Without automated enforcement, untested code can slip through reviews.

Agentic, autonomous ITOps improves incident response by carrying context from detection through resolution, reducing noise, delay, and manual coordination. Most IT incidents don’t fail due to missing data. Monitoring systems generate more than enough signals. The problem is that understanding those signals—and deciding what to do with them—happens in fragments. Engineers move between dashboards, logs, tickets, and chat threads, stitching together context by hand.

If you work in network operations, you know that the only constant is the increasing complexity of the infrastructure you manage. The days of installing a monolithic software package on a single bare-metal server and letting it hum along for years are largely behind you. The software industry has largely shifted toward cloud-native architectures, microservices, and containerization. While these shifts promise agility and scalability, they also introduce significant operational complexity.

For decades, IT operations have been built around incidents, SLAs, and ticket closure rates. Success has been defined by how quickly tickets are resolved and whether service levels are met. But the modern digital workplace has changed. Employee productivity, digital adoption, collaboration quality, and business performance depend on far more than ticket metrics. A device that “works” but performs poorly still erodes productivity.