- JDK (
1.8+
) - Maven (
3.x
) - Please make sure Docker Desktop is installed and Kubernetes is activated. Read this for details.
- Please make sure Kubernetes CLI (
kubernetes-cli
/kubectl
) is installed. See here for details.
This setup shows how you can install OpenTelemetry resources into Kubernetes first and deploy application later then. So deployed applications will be auto instrumented.
- Replace
<CATCHPOINT-TRACING-API-KEY>
with your Catchpoint Tracing API key inotel/collector.yaml
file. - Then run the setup script which installs OpenTelemetry Operator and OpenTelemetry Instrumentation CR (Custom Resource) into Kubernetes:
./otel/setup-otel.sh
- Run the deployment script which deploys database and applications with OpenTelemetry configuration into Kubernetes:
./apps/deploy-apps-with-otel-conf.sh
- Wait until all services are activated.
- Go to http://localhost:30000.
- Run the deployment script which deploys database and applications without OpenTelemetry configuration into Kubernetes:
./apps/deploy-apps.sh
- Wait until all services are activated.
- Go to http://localhost:30000.
- Replace
<CATCHPOINT-TRACING-API-KEY>
with your Catchpoint Tracing API key inotel/collector.yaml
file. - Then run the setup script which installs OpenTelemetry Operator and OpenTelemetry Instrumentation CR (Custom Resource) into Kubernetes:
./otel/setup-otel.sh
- Run the patch script which updates application deployments by adding OpenTelemetry Auto Instrumentation Annotation (
instrumentation.opentelemetry.io/inject-java
) to the services to be traced:./apps/patch-apps-with-otel-conf.sh
- Wait until all services are restarted.
- Go to http://localhost:30000.
- Run the application destroy script which deletes applications and database deployed to Kubernetes:
./apps/destroy-apps.sh
- Wait until all resources are deleted.
- Run the OpenTelemetry destroy script for deleting the OpenTelemetry resources (operator and instrumentation CR),
./otel/destroy-otel.sh
- Wait until all resources are deleted.