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:
To do so, Arnau, their DevOps manager, proceeds to:
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 Zero Configuration Automatic Instrumentation for Kubernetes Java applications to set up Auto Intrumentation for their clinic apps.
After completing the deployment, Arnau is able to see the results using APM.
Arnau uses the Collector and the upstream Kubernetes Operator to auto-instrument their Java applications and see the results in APM dashboards.