Operations | Monitoring | ITSM | DevOps | Cloud

Take a quick walkthrough of what’s new in the updated OnPage Enterprise Management Console. In this video, we highlight the latest updates designed to give admins more visibility, flexibility and self-service control across critical communication workflows. You’ll see what’s new across the console, including: The updated Enterprise Management Console helps teams manage on-call schedules, critical alerts, escalation workflows and Dedicated Lines more efficiently from one centralized place.

Learn how override schedules work in OnPage and how admins can quickly manage temporary on-call coverage changes without rebuilding the entire schedule. With OnPage overrides, teams can adjust coverage for vacations, sick days, shift swaps, after-hours changes or last-minute availability issues. During the override window, alerts are automatically routed to the covering responder. Once the override ends, the schedule returns to the regular on-call rotation.

Every dependency pull is a trust decision. Public registries don't vet what they serve. Cooldown policies give you a gate at the moment that matters most: when a package first enters your environment. Dan McKinney (Solutions Engineering Manager) walks through how Cloudsmith's cooldown policies work and how to configure one in under five minutes. What Dan covers.

Most platform engineering stories are told in hindsight, with the rough edges smoothed out. On June 17th, we are doing it differently. Join us for Platform Engineering Unplugged, a frank conversation with a practitioner who has navigated the real challenges of building and scaling platform engineering. What worked, what didn't, and what they would do differently. If you lead engineering teams and are thinking seriously about platform engineering, this is the session for you.

With AirDroid Parental Control, parents can understand how AI is used in homework, spot unusual queries, and help kids build healthier learning habits.

Bad data doesn't announce itself. Datadog Data Observability gives you unified visibility across your entire data stack—from source systems and pipelines to dashboards and AI applications—so you catch silent failures before they cascade. Detect data quality and pipeline issues before stakeholders do, pinpoint root causes with end-to-end lineage, and reduce pipeline costs with job, cluster, and query recommendations.

Tired of noisy alerts waking you up for issues that are not actually impacting your services? In this tutorial, we walk through MetricFire's Composite Alerting capabilities and show how to combine multiple metric conditions into a single high-confidence alert using AND / OR logic. Learn how to: Reduce alert fatigue and false positives Create service level alerts in Graphite Combine CPU, latency, and database metrics into meaningful alerts Use conditional logic to improve signal quality Build smarter observability workflows with Hosted Graphite.

Who really owns your data? Data sovereignty has become one of the defining issues shaping digital infrastructure, cloud strategy and AI adoption. But what does it actually mean, and why has it become a board-level discussion for so many organisations? In Episode 4 of Perspectives from the Edge, Pulsant's Wendy Shearer is joined by Steve Jewell, CEO of Nine23, to explore data sovereignty and its relationship to security, resilience and digital transformation.

Customer interviews are one of the most powerful ways to build better products — but they’re also time-consuming. In this video, Avinoam “Avi” Zelenko, Principal Product Manager at Atlassian, shares how he transformed the way he runs customer interviews using AI automation and Rovo agents. What used to take hours of coordination, note-taking, and manual summaries now happens automatically. By stitching together the Teamwork Collection and Slack, Avi built a workflow that captures conversations, summarizes insights, and shares them across teams in real time.

Azure integration errors can be difficult to diagnose when messages flow across multiple services such as Logic Apps, Service Bus, Azure Functions, APIs, and external systems. Support teams often spend hours searching through logs and correlating events across services just to identify where a transaction failed.