Operations | Monitoring | ITSM | DevOps | Cloud

No matter how fast we build, we'll never integrate with every tool. There are too many, new ones appear constantly, and some are too niche to ever reach the top of our roadmap. So if the tool you care about isn't supported yet, your options have been to wait for us to get to it, or build it yourself with our Web API plugin — a powerful, flexible option, though one that asks you to map out the endpoints, authentication and paging yourself.

There’s a lot happening across Asia Pacific right now. Enterprises are moving quickly to modernize operations, adopt AI, and manage growing complexity across increasingly distributed environments, and the opportunity ahead for LogicMonitor in the region continues to grow alongside it. That’s why I’m especially excited to welcome Dave Patnaik to LogicMonitor as our new Vice President of APAC.

Obkio is proud to announce an important investment from Devolutions, one of the most respected names in IT security and remote access management. This investment marks a new chapter for Obkio as we accelerate our next phase of growth. This isn't a financial transaction between strangers. It's a partnership between two companies that have spent years building tools for the same people: IT professionals, sysadmins, MSPs, and the network engineers who keep critical network infrastructure running.

Modern production environments generate massive volumes of logs every day. As systems become more distributed and cloud-native, that volume only increases. The real challenge isn’t collecting logs—it’s identifying what matters fast enough to act using effective log visualization. Most log views fail at this point. Every entry looks the same, forcing engineers to scan them manually and interpret lines under pressure.

The OpenTelemetry Collector is usually deployed as a long-running process: a sidecar, a DaemonSet, an EC2 instance, a docker container on my computer. It sits there listening for telemetry. That's fine when I want to send telemetry all day, but not when telemetry is rare. Like right now, when I have an agent defined on AgentCore, and it runs a few times a week maybe. Or my website that hardly sees any traffic. Can I run the OpenTelemetry Collector as a Lambda function?

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.

Sentry’s SDK teams maintain and support SDKs for a vast ecosystem of languages and frameworks. See our release registry for a source of truth. We’re currently at 159 published packages across the entire ecosystem. If you use it, we probably support it. All of these SDKs are open source and have their own GitHub repositories that we maintain on a daily basis. And like any other open source project, we get tons of bug reports and issues on these.

You open a monitoring tool, and the data is all there: errors, traces, anomalies, incidents, and countless intricacies. If you want to get the right slice of that data, you need to know exactly which dashboard to open and what filters to apply. But when the poor UI gets in the way, this can take longer than it should. Luckily, this is not the case with AppSignal. MCP (Model Context Protocol) changes the interface entirely.