Skip to content

Commit 003c8ba

Browse files
committed
Refactor of Pet-Clinic workshop
1 parent ce6be23 commit 003c8ba

File tree

3 files changed

+39
-43
lines changed

3 files changed

+39
-43
lines changed

content/en/pet-clinic/_index.md

Lines changed: 29 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,5 +3,33 @@ title: Pet Clinic Java Workshop
33
cascade:
44
type: docs
55
description: >
6-
Environment Configuration and Hands-On Exercises
6+
Introduction
77
---
8+
9+
The goal is to walk through the basic steps to configure the following components of the Splunk Observability platform:
10+
11+
* Splunk Infrastructure Monitoring (IM)
12+
* Splunk Zero Configuration Auto Instrumentation for Java (APM)
13+
* Database Query Performance
14+
* AlwaysOn Profiling
15+
* Splunk Real User Monitoring (RUM)
16+
* Splunk LogsObserver (LO)
17+
18+
We will also show the steps about how to clone (download) a sample Java application (Spring PetClinic), as well as how to compile, package and run the application.
19+
20+
Once the application is up and running, we will instantly start seeing metrics and traces via the Zero Configuration Auto Instrumentation for Java that will be used by the Splunk APM product.
21+
22+
After that, we will instrument the PetClinic's end user interface (HTML pages rendered by the application) with the Splunk OpenTelemetry Javascript Libraries (RUM) that will generate RUM traces around all the individual clicks and page loads executed by an end user.
23+
24+
Lastly, we will configure the Spring PetClinic application to write application logs to the filesystem and also configure the Splunk OpenTelemetry Collector to read (tail) the logs and report to Splunk Observability Cloud.
25+
26+
{{% alert title="Prerequisites" %}}
27+
A Splunk run workshop where an host/instance is provided **OR** a self led workshop on own host / [multipass instance](https://github.com/splunk/observability-workshop/tree/main/multipass)
28+
29+
For your own system you will need the following installed and enabled:
30+
31+
1. Java installed
32+
2. Port `8080` open inbound/outbound
33+
{{% /alert %}}
34+
35+
![PetClinic Exercise](images/petclinic-exercise.png)

content/en/pet-clinic/docs/intro.md

Lines changed: 0 additions & 32 deletions
This file was deleted.

content/en/pet-clinic/docs/rum.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -19,16 +19,16 @@ Then you'll need to select the workshop RUM token and define the application and
1919

2020
Copy the generated code snippet in the wizard or copy and edit the snippet below accordingly:
2121

22-
```html
23-
<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>
24-
<script>
25-
SplunkRum.init({
26-
beaconUrl: "https://rum-ingest.<REALM>.signalfx.com/v1/rum",
27-
rumAuth: "<RUM_ACCESS_TOKEN>",
28-
app: "<hostname>-petclinic-service",
29-
environment: "<hostname>-petclinic-env"
30-
});
31-
</script>
22+
``` html
23+
<script src="https://cdn.signalfx.com/o11y-gdi-rum/latest/splunk-otel-web.js" crossorigin="anonymous"></script>
24+
<script>
25+
SplunkRum.init({
26+
beaconUrl: "https://rum-ingest.<REALM>.signalfx.com/v1/rum",
27+
rumAuth: "<RUM_ACCESS_TOKEN>",
28+
app: "<hostname>-petclinic-service",
29+
environment: "<hostname>-petclinic-env"
30+
});
31+
</script>
3232
```
3333

3434
The Spring PetClinic application uses a single HTML page as the "layout" page, that is reused across all pages of the application. This is the perfect location to insert the Splunk RUM Instrumentation Library as it will be loaded in all pages automatically.

0 commit comments

Comments
 (0)