Operations | Monitoring | ITSM | DevOps | Cloud

ManageEngine has been recognized in the Gartner® Magic Quadrant™ for Digital Experience Monitoring for two consecutive years! We believe this reinforces our consistent efforts to help business achieve business excellence.

For many organizations, periods of high customer activity are anything but relaxing. Events like Black Friday, product launches, or major sales can put intense strain on the software and infrastructure systems that support a company’s web applications. Without proactive performance testing, these moments can quickly turn into poor user experiences and lost revenue.

Managing team access in Grafana can be tricky—especially as your organization grows. That’s where Grafana access groups (also known as Limited Access Groups in Hosted Graphite) come in. They allow you to define groups of dashboards and restrict which team members can access them. If you’re using Hosted Graphite with Grafana dashboards, this feature helps you organize teams, maintain data privacy, and simplify access control—all while giving users just the permissions they need.

At LogicMonitor’s Senior Leadership Team Offsite in July, I sat down for a candid conversation with Kyle Hill, CTO of ANS Group. As a longtime LogicMonitor customer and leader of a 700+ person tech powerhouse, Kyle offered sharp insights into scaling infrastructure, unlocking AI-driven value, and what true partnership looks like in today’s MSP world. Here’s an edited and condensed version of our conversation.

Go’s os.Root feature, introduced in Go 1.24, is designed to improve filesystem security by restricting operations to a specific directory, making it much harder for attackers to exploit path traversal vulnerabilities.

Some parts of a system don’t lend themselves to quick instrumentation changes. You might have a production binary that hasn’t been rebuilt in years, or a stack made of several languages where each team manages telemetry differently. In those situations, getting consistent signals often means touching code you’d rather leave alone or coordinating updates across many services. OpenTelemetry eBPF Instrumentation (OBI) approaches this from the kernel side.

There’s a viral saying folks use about flaky crushes, spouses, and forgetful friends: "if he wanted to, he would." The idea is straightforward: when someone cares, they make the effort. As it turns out, the same principle applies surprisingly well to AI. Systems, like people, have things they "want" to do. Each model has patterns of reasoning and synthesis it performs naturally.

Some of the team at Sentry spent this past quarter fixing bugs, more than 800 to be exact. Among them was a complex issue causing transaction spikes in our own Sentry project. Using Sentry Logs, we were able to investigate, trace the root cause, and resolve the problem.

Active Telemetry is the evolution in how organizations collect, process, and use observability data. In traditional observability, telemetry is passive: systems emit logs, metrics, and traces that are stored and visualized after the fact. This model worked when systems were simpler and changes were predictable. But in today’s world with distributed microservices, Kubernetes, and AI workloads, passive telemetry can’t keep up. Active Telemetry changes that.

The digital landscape has transformed dramatically, and with it, the demands on our systems have grown exponentially. Traditional monitoring tools struggle to provide sufficient insight into complex, distributed, cloud-native environments. Observability is the answer, moving beyond merely knowing "what" is happening to understanding "why" it's happening, and its impact on user experience and business outcomes.