Operations | Monitoring | ITSM | DevOps | Cloud

An Overview of the OpenTelemetry Collector's Configuration File

In this video, I’ll provide an overview of the OpenTelemetry Collector’s configuration file (config.yaml) with examples from the Splunk distribution. I will briefly explain the components of the Splunk OTel Collector, and walk you through a sample generic configuration of the OTel Collector. We’ll then use the Splunk Observability Cloud interface to construct the commands needed to install the Splunk OTel Collector on a specific host. This installation will copy a default Splunk OTel Collector configuration onto the host, and we’ll review the Splunk specific components of this configuration.

Unlock the Value of Cloud: Introducing Splunk Cloud Value Calculator

In the rapidly evolving digital landscape, organizations are increasingly turning to the cloud powered with AI capabilities to enhance efficiency, scalability and innovation. Splunk, a leader in security and data observability, has been at the forefront of this transformation.

Setting up and Understanding OpenTelemetry Collector Pipelines Through Visualization

Observability provides many business benefits, but comes with costs as well. Once the (not-insignificant) work of picking a platform, taking an inventory of your applications and infrastructure, and getting buyin from leadership (both from the business and engineering sides of the house) is done, you then have to actually instrument your applications to emit data, and build the data pipeline that sends that data to your observability system.

Install The Splunk Distribution of OTel Collector in K8s with Helm

In this video, I’ll show you how to install the Splunk Distribution of the OTel Collector using a Helm Chart. We’ll walk through constructing the necessary Helm commands using the K8s Integration Wizard in Splunk Observability Cloud, and then deploy the collector to a cluster. We’ll then verify that the cluster and its services are being monitored in Observability Cloud’s Kubernetes Navigators, and then briefly walk through the values.yaml file of the Helm chart as well as the Otel Collector’s configuration.

Chaos Testing Explained

Chaos testing is a part of site reliability engineering (SRE). In chaos testing, we intentionally break things in and around a given application, in order to: The purpose of chaos testing is to assess how software systems respond to scenarios like network outages, hardware failures, database failures, and server or cluster node failures in the infrastructure.

Building an AI Assistant in Splunk Observability Cloud

Splunk Observability Cloud is a full-stack observability solution, combining purpose-built systems for application, infrastructure and end-user monitoring, pulled together by a common data model, in a unified interface. This provides essential end-to-end visibility across complex tech stacks and various data types, such as metrics, events, logs, and traces (MELT), as well as end-user sessions, database queries, stack traces and more.

Uncomplicate SLOs to Deliver Digitally Resilient Systems and Better Customer Experiences

If your organization has an observability practice, it’s likely that the end goal was to increase system reliability and customer satisfaction. But balancing reliability needs with the need to innovate to meet ever-increasing customer expectations remains a challenge for most.

Build Resilient Connections in Communications and Media with Splunk

In our super connected world, the Communications and Media industry has a lot on the line. Your networks help people stay in touch, get around-the-clock care, and protect their nest eggs. Expectations are incredibly high. And reliability is a must. At Splunk, we help Communications and Media organizations build resilient digital systems.