Operations | Monitoring | ITSM | DevOps | Cloud

Top tips: Designing systems people won't work around

Top tips is a weekly column where we highlight what’s trending in the tech world today and list ways to explore these trends. This week, we’re looking at why people bypass systems—and how better design choices can prevent it. When people work around systems, it’s tempting to blame their behavior. In reality, most employee workarounds are signals.

VirtualMetric's Hybrid Security Data Collection Architecture: Performance and Scale Without Compromise

Modern security operations face a growing architectural challenge: collect telemetry from everywhere, process it in real time, and route it to multiple platforms while maintaining data sovereignty, avoiding agent sprawl, and keeping costs under control. Single-model collection strategies force security teams to make compromises. Agent-only models create operational overhead and maintenance risk. Agentless-only approaches simplify operations but limit depth and flexibility.

The next wave of AI: Open source, robotics & the future of India's tech powerhouse

As we kick off 2026, the tech landscape is being reshaped by the very breakthroughs discussed at Civo Navigate India 2025. This panel, featuring Josh Mesout, Murthy Chitlur, Chirotpal Das and Anjali Batra, laid the groundwork for the AI-driven world we are operating in today. From the rise of agentic AI and small language models to the massive shift toward open-source parity, these experts didn't just discuss trends; they provided the blueprint for building resilient, sovereign, and scalable AI infrastructure in India.

Observability with AI? Honeycomb with AI!

Since Honeycomb started, it has had a weakness: too many choices. Every field, custom or standard, hundreds of them, all are free to group, filter, and visualize in dozens of ways. Which ones are interesting? Honeycomb exists to help people understand custom software. It doesn’t pretend to know what matters in your application. That’s an interpretive task, not programmatic. Hey, computers can do interpretation now!

DevTalk | Mobile Computing AI Suite | Product Recognition and advanced features | Zebra

Join us for the second session of our DevTalk series as we explore the powerful capabilities of Zebra's Mobile Computing AI Suite. This webinar covers how our Zebra Frontline AI Enablers equip developers with a software development kit (SDK), sample applications, and APIs to integrate AI-powered computer vision features into enterprise applications on Zebra mobile devices. These tools are designed to accelerate development by providing pre-trained models and sample code specifically optimized for the Qualcomm AI-accelerated hardware in Zebra's devices.

Lightrun Runtime Context MCP | Lightrun

In this video, Lightrun's Moshe Sambol walks you through the power of Lightrun MCP and Runtime Context. A game-changer for AI-assisted development. This integration lets developers debug live issues, inspect real-world variables, and verify fixes across environments, all without leaving the IDE. With Lightrun MCP, you can: Capture live transaction state directly from Staging and Production. Identify root causes using real runtime values, not just static code. Verify fixes instantly without redeploying or context switching.

High Cardinality Metrics: How Prometheus and ClickHouse Handle Scale

TL;DR: Prometheus pays cardinality costs at write time (memory, index). ClickHouse pays at query time (aggregation memory). Neither is "better":they fail differently. Design your pipeline knowing which failure mode you're accepting. -- Every month, someone posts "just use ClickHouse for metrics" or "Prometheus can't handle scale." Both statements contain a kernel of truth wrapped in dangerous oversimplification.

Showcasing open design in action: Loughborough University design students explore open source projects

Last year, we collaborated with two design student teams from Loughborough University in the UK. These students were challenged to work on open source project briefs. Team 1 focused on non-code contributions, while Team 2’s brief was to create a unified documentation experience, giving them a chance to apply their design skills to real-world problems within the open source ecosystem.