Operations | Monitoring | ITSM | DevOps | Cloud

Today we’re thrilled to announce the launch of Entity Relationships, a powerful new capability that gives you more flexibility and control over the data model in your IDP. By allowing you to create custom relationships between entities in your catalog, you can model your internal developer portal to accurately reflect your own organization’s taxonomy, letting you better answer deep questions about your environments, releases, packages, and beyond.

Pulseway and Kaseya have worked side by side for years, driven by a shared goal: to make powerful, easy-to-use IT solutions accessible to small and midsized businesses (SMBs). With the release of Pulseway 9.15, the merger becomes a reality into the product, with new features and a path for innovation. This update marks the beginning of a deeper alignment between the two platforms, giving Pulseway users direct access to the benefits of Kaseya's broader ecosystem.

We’re excited to share that Icinga for Kubernetes v0.3.0 is here! This release is packed with features designed to make monitoring your Kubernetes environments smoother, smarter, and more efficient. Let’s take a closer look at what’s new.

Today, we are pleased to announce the release of CFEngine 3.26.0! Being a non-LTS (not supported) release, this release allows users to test the new functionality we’ve been working on before it arrives in an LTS release later this year. The codename for this release is a bit different, as it is named after a new feature introduced, and what it eliminates - the admin user.

As organizations move beyond traditional hypervisors, Harvester continues to lead the way as an open source, Kubernetes-native virtualization solution. With the release of Harvester 1.5, users now have greater flexibility and ecosystem alignment than ever before—with General Availability (GA) for ARM64 and support for CSI-compatible storage backends. Harvester is part of a growing shift toward cloud-native infrastructure that unifies VMs and containers under the Kubernetes API.

You’re looking at an error in Sentry—a failed payment in your Flask backend or an unexpected null in your Node API. You’ve got the stack trace. The request details. Even the full trace. What you don’t have: the logs your app emitted right before everything went sideways. With Sentry Logs (now in open beta), you can send application logs straight to Sentry and see them automatically connected to the errors and traces you already use.

You shipped your latest release. You tested it on emulators, QA devices, and the latest OS versions. But now it’s live and running on thousands or millions of mobile devices, across a jungle of screen sizes, hardware specs, OS versions, and network conditions. A user reports a crash on an old Samsung device over 3G. Someone else complains the app feels “sluggish” after updating. You dig through logs. Rebuild test cases. Ping the backend team. Try to reproduce. Yet, still no answers.