Operations | Monitoring | ITSM | DevOps | Cloud

Many engineering teams rely on ElasticSearch for search and analytics, but as data volumes grow, so do the challenges of scale, cost, and performance. At Mezmo, we faced this reality head-on, recognizing the need for a more efficient and scalable solution to support our multi-cluster, multi-petabyte telemetry data backend. After extensive evaluation, we made the leap to Quickwit, an open-source, cloud-native search engine for logs. But making such a fundamental architectural shift—without disrupting customers—was no small feat.

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.

When something goes wrong with your microservice-based apps, Splunk Observability Cloud offers a unified Observability platform to make debugging processes easier and faster. By using features like the Service Map to identify the cause of the error and Related Logs in Log Observer to pinpoint its location, you can get back up and running quickly, limiting the impact to your bottom line and keeping your customers happy.

Check out the full ‪‪@bindplane‬ OTel deep dive workshop.