Docs » Get started with the Splunk Distribution of the OpenTelemetry Collector » Splunk OpenTelemetry Zero Configuration Auto Instrumentation » Splunk OpenTelemetry Zero Configuration Auto Instrumentation for Java » Scenario: Arnau instruments Java apps using the Splunk Collector and Kubernetes Operator

Scenario: Arnau instruments Java apps using the Splunk Collector and Kubernetes Operator 🔗

Spring Clinic Microservices, a fictitious company, wants to use the OTel Collector and the upstream Kubernetes Operator to auto-instrument their Java applications. The final architecture will look as shown in the diagram below:

Java app auto instrumentation architecture diagram.

To do so, Arnau, their DevOps manager, proceeds to:

  1. Set up the apps to instrument.

  2. Deploy and configure the Collector.

Note

Learn more about the Spring Clinic Microservices demo in GitHub at spring-petclinic/spring-petclinic-microservices .

1. Set up the applications to instrument 🔗

Arnau creates the spring-petclinic namespace and deploys the related Java applications to it.

kubectl apply -f examples/enable-operator-and-auto-instrumentation/spring-petclinic -R

2. Deploy and configure the Collector 🔗

Arnau follows the steps described in Install the Collector and the upstream Kubernetes Operator for Auto Instrumentation to set up Auto Intrumentation for their clinic apps.

After completing the deployment, Arnau is able to see the results using APM.

Java app auto instrumented.

Summary 🔗

Arnau uses the Collector and the upstream Kubernetes Operator to auto-instrument their Java applications and see the results in APM dashboards.

Learn more 🔗

To install the Operator for Auto Instrumentation, see Install the Collector with the Kubernetes Operator.