Operations | Monitoring | ITSM | DevOps | Cloud

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.

Every time your app asks the database 'does this row exist,' it pays the cost of a database query to get back 'no'.

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.

A Hardware Asset Management (HAM) audit is a formal check of whether your hardware inventory reflects physical reality. It covers what devices exist, where they are, who has them, what state they're in, and how retired assets were documented out of the system. Most organizations don't fail HAM audits because their IT teams are negligent.

Standardize the route from code to production. Everything else is a team decision, not a platform problem. Most app delivery problems do not start with bad engineering. They start with too much variation. One team provisions environments manually. Another keeps deployment notes in a wiki. A third has a staging setup that only one engineer understands. Security reviews happen late because the platform does not make the safe path obvious.

When a critical system goes down, the clock starts ticking. Every minute matters. Whether it’s a cloud platform, manufacturing operation, logistics center, airport infrastructure, or business-critical software, downtime creates more than just technical issues — it often leads to significant financial losses. That’s where MTTR comes in. MTTR measures how long it takes an organization, on average, to restore normal operations after an incident.

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.

Dear Nexthink community, We are excited to be named a Leader in the 2026 Gartner Magic Quadrant for Digital Employee Experience Tools for the third year in a row. I want to share this recognition with our customers, our partners and ecosystem, and every Nexthinker across the world. As a founder, it’s a true honor to work alongside so many talented people. To us, this recognition is also yours.

A software engineer's hands-on journey building a private cloud on bare-metal: Incus clustering, K3s, OVN networking, the Gateway API, and everything that breaks along the way — and what it taught them about why platforms like Qovery exist. Antoine is a senior software engineer at Qovery. He writes about hands-on infrastructure engineering, Kubernetes internals, and the realities of running production systems.