Stop letting broad averages hide your system's reality. A low compliance rate tells you a service is failing, but it doesn't tell you why. To fix it, you have to separate planned noise from actual technical debt. In this video, we break down two distinct ways New Relic Service Levels help you move from vague alerts to precise resolution. Topic 1: Stop Wasting Your Error Budget Scheduled deployments and database tests shouldn't look like system failures. We show you how to use Maintenance Windows to exclude planned downtime from your calculations. By silencing this noise, you ensure your service levels only reflect the unplanned incidents that actually impact your customers. Topic 2: Unmask the Root Cause with Faceting A single service level can hide failures occurring in specific pods or API endpoints. We demonstrate how to use faceting to break a single SLI into its component parts. This allows you to identify exactly which group is pulling down your compliance without having to build and manage dozens of individual service levels. Inside the video: 0:00 - Why broad SLIs mask critical issues | 0:22 - Maintenance Windows: Protecting the error budget | 0:50 - Scheduling recurring deployment windows | 1:05 - Faceting: Deconstructing the global average | 1:40 - Real-world demo: Isolating a failing endpoint in seconds | 2:20 - Reclaiming engineering time with precise data Subscribe to the channel → https://www.youtube.com/c/NewRelicInc?sub_confirmation=1 Follow New Relic on: New Relic → https://newrelic.com Twitter → https://twitter.com/NewRelic LinkedIn → https://www.linkedin.com/company/new-relic-inc- Facebook → https://www.facebook.com/NewRelic

 175      6