...
Tip |
---|
When the application is up and running and the Sealights Listener agent configured, you can it is properly running from the Cockpit -> Agent Monitor screen.
|
Warning |
---|
If the agent does not appear in the Cockpit Agent Monitor when your application is up and running, you can turn on the logging of the Sealights agent by adding one or both of the following parameters:
More details about these parameters are detailed in a dedicated documentation section https://sealights.atlassian.net/wiki/spaces/SUP/pages/1933323/SeaLights+Java+agent+-+Command+Reference#Logging |
...
Kubernetes using an Init container
In the sample Yaml YAML file below, we dynamically download the agent into a side car sidecar container to make it available to the JVM of our application container
...
. We’re using a lightweight base image that contains wget
and unzip
.
Code Block | ||
---|---|---|
| ||
spec: initContainers: - name: sealights-java-cdcoverage-agentlistener image: busyboxalpine:latest imagePullPolicy: IfNotPresent command: ["/bin/sh", "-c"] args: - | wget -nv -O /tmp/sealights-java-agents.zip https://agents.sealights.co/sealights-java/sealights-java-latest.zip; mkdir -p /sealights; unzip -j /tmp/sealights-java-agents.zip sl-test-listener.jar -d /sealights; volumeMounts: - mountPath: /sealights name: sealights-java-coverageagent-listenerfile containers: - name: your-app-mainservice-container # other container configurations env: - name: sl.tagsJAVA_TOOL_OPTIONS value: k8s - name: sl.labId value: integ_test_microservices - name: JAVA_TOOL_OPTIONS value: -"-javaagent:/sealights/sl-test-listener.jar -Dsl.labId={{ .Values.SealightsEnvVars.lab_id }} -Dsl.tags=k8s" volumeMounts: - mountPath: /sealights name: sealights-java-coverageagent-listenerfile volumes: - name: sealights-java-coverageagent-listenerfile emptyDir: {} |
JBoss & Wildfly
...