In this walkthrough, Zack from New Relic demonstrates how to break down the silos between your performance data and your business context. Usually, correlating telemetry (New Relic) with customer data (Snowflake, BigQuery, Google Sheets, etc.) requires expensive ETL pipelines or "spreadsheet gymnastics" during an active incident. New Relic Lens changes the game by introducing a federated query engine. Treat your external databases like just another table inside New Relic—no data movement required. Key Takeaways: Federated Querying: Query Snowflake, Postgres, AWS CloudWatch, and more in place. Business-Aware Triage: Stop looking at broken microservices and start looking at revenue at risk. Collaborative Analysis: Turn technical queries into shared Notebooks for Product and Sales teams. Timestamps 0:00 Something is Missing 0:12 Defining the Visibility Gap 0:23 Introducing New Relic Lens 0:30 The Problem: Siloed Data (Performance vs Business Telemetry) 0:59 How the Federated Query Engine Works 1:15 Setting up a Connector in less than 60 Seconds 1:30 Joining New Relic and Business Telemetry using SQL 2:03 Summary: Federated Querying, Business-aware Triage, and Collaborative Analysis 2:45 Get Started Today Resources & Links Try New Relic Lens: https://newrelic.com/platform/product-preview New Relic Documentation: https://docs.newrelic.com/docs/new-relic-lens/overview/ 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

 284      15