In this tutorial, we’ll demonstrate how to create and use private locations in Splunk Synthetic Monitoring to test internal or pre-production applications within a Kubernetes environment. You'll learn exactly what private locations and private runners are, common use cases, and step-by-step instructions on how to deploy a private runner using Helm. Finally, you'll see how to set up a simple browser test to run synthetics against a service available only within a Kubernetes cluster. Try Splunk Observability Cloud free for 14 days: https://splunk.com/o11y-trial Splunk Observability Hub: https://splunk.com/observabilityhub Related videos: Introduction to Splunk Synthetic Monitoring in Splunk Observability Cloud - https://youtu.be/_CvbiwSFGNk?si=tYd3M2xjG3i2C5sR Set up browser tests in Splunk Synthetic Monitoring using the Chrome DevTools Recorder - https://youtu.be/eQ_EQvjGAK8?si=j0VUtmVXR2BAomUW Real-world Synthetics: Browser testing ECommerce with Splunk - https://youtu.be/A1D9IJ2qa1U?si=QnjgbUy20A8cmzVy TOC: Introduction 00:00 What are private locations? 00:08 The Kubernetes environment 01:21 Create and deploy a new private location 04:05 Create a synthetic test 06:33 View test runs 08:05 Private runner metrics 09:37 Conclusion 10:50

 243      7