Operations | Monitoring | ITSM | DevOps | Cloud

The last few years have felt less like a product roadmap and more like a scene from science fiction. Artificial intelligence didn’t simply arrive, it erupted. In what feels like a blink, we’re building software by prompting instead of programming. Our words now generate code, compose music, translate languages, and create entire digital experiences.

As teams grow and telemetry scales, it becomes harder to keep track of which metrics matter. Labels pile up, cardinality increases, and costs start rising faster than anyone expected. At the same time, dashboards often stay quiet and alerts go untouched. The truth is, most teams don’t actually know how and how much of their metric data is being used, let alone which metrics are driving cost. This is exactly the problem we set out to solve.

HAProxy 3.3 is here, and this release brings downloadable packages compiled by HAProxy Technologies, numerous TLS enhancements including expanded ACME support, better observability with persistent stats over reloads, and many improvements to performance and flexibility such as support for QUIC on the backend. These powerful capabilities help HAProxy remain the G2 category leader in API Management, Container Networking, DDoS Protection, Web Application Firewall (WAF), and Load Balancing.

Shai-Hulud 2.0 shows how quickly a compromised maintainer account can result in thousands of infected NPM packages and repositories within hours. Harness SCS provides end-to-end SBOM visibility, policy enforcement to block compromised NPM packages, and complete traceability to detect malicious components early and prevent them from entering your pipelines.

Harness Database DevOps was born from a simple question - how can database delivery be as seamless and safe as application delivery? Through deep collaboration with design partners, open-source learnings, and relentless iteration, the team built a platform that unites developers, DBAs, and DevOps under a single, automated workflow. At its core, it’s a story of empathy-driven engineering - transforming database change management into a faster, more reliable, and collaborative experience.

Harness makes software delivery in AWS faster, safer, and more delightful. Harness, the AI Platform for Everything After Code, offers CI/CD, infrastructure-as-code management, and cloud cost management capabilities tailored to the AWS environment. Harness has come a long way since its 2019 debut on the AWS Marketplace. Back then, over half of Harness customers were already running on AWS, and Harness focused on delivering Continuous Delivery as a Service for AWS applications.

Your remote developer can't access the VPN. Is it his home router? His ISP? Your network? You have no idea and no way to find out. This is the reality of modern IT. Your network doesn't end at your office perimeter. It extends into hundreds of homes, coffee shops, branch offices, and third-party locations you'll never set foot in. And when performance tanks, you're troubleshooting blind.

Log management and Network Detection and Response (NDR) solutions are closely related but offer different layers of visibility. Rather than overlapping, they complement each other, together providing a connected view of what’s happening in your environment. How exactly? Let’s take a closer look.

Observability data has a habit of outgrowing everything else. As telemetry volume, variety, and velocity increases, staying organized gets harder. Governance becomes messy, and the cost of digging through “everything” keeps rising. Over the past year, Coralogix’s DataPrime engine has been addressing these challenges by laying a new foundation for observability at scale.

Tracing is one of the most transformative gifts of observability. It allows engineers to follow a single request through a distributed system and see every span and dependency along the way. However, even with that visibility, some of our most basic questions stay unanswered. Why did a specific span behave differently today than it did yesterday? Why did latency rise even when nothing “broke”?