Refactored to support Java 2.x

Author: rcastley

content/en/other/3-automatic-discovery/2-petclinic-kubernetes/3-verify-setup/2-section-break.md

@@ -2,6 +2,7 @@
 title: Configuring Logback
 linkTitle: 1. Configure Logback
 weight: 1
+hidden: true
 ---
 
 First, clone the PetClinic GitHub repository, as we will need this later in the workshop to compile, build, package and containerize the application:

content/en/other/3-automatic-discovery/2-petclinic-kubernetes/4-apm/3-section-break.md

@@ -1,16 +1,14 @@
 ---
 title: Viewing the Logs
-linkTitle: 4. Viewing the Logs
-weight: 4
+linkTitle: 1. Viewing the Logs
+weight: 2
 ---
 
 In order to see logs click on the **Log Observer** ![Logo](../../images/logo-icon.png?classes=inline&height=25px) in the left-hand menu. Once in Log Observer please ensure **Index** on the filter bar is set to **splunk4rookies-workshop**.
 
 Next, click **Add Filter** and search for the field `deployment.environment`, select your workshop instance and click `=` (to include). You will now see only the log messages from your PetClinic application.
 
-Next search for the field  `service_name`, select the value `customers-service` and click `=` (to include). Now the log entries will be reduced to show the entries from your `customers-service` only.
-
-In the log entry you will see the message is formatted as per the pattern we configured for logback eariler **(1)**:
+Next search for the field  `service.name`, select the value `customers-service` and click `=` (to include). Now the log entries will be reduced to show the entries from your `customers-service` only.
 
 ![Log Observer](../../images/log-observer-trace-info.png)
 

content/en/other/3-automatic-discovery/2-petclinic-kubernetes/5-traces/5-section-break.md

@@ -2,6 +2,7 @@
 title: Rebuild PetClinic
 linkTitle: 2. Rebuild PetClinic
 weight: 2
+hidden: true
 ---
 
 Before we can build the new services with the updated log format we need to add the OpenTelemetry dependency that handles field injection to the `pom.xml` of our services:

content/en/other/3-automatic-discovery/2-petclinic-kubernetes/6-profiling-db-query/4-section-break.md

@@ -1,15 +1,15 @@
 ---
 title: Related Content
-linkTitle: 5. Related Content
-weight: 5
+linkTitle: 2. Related Content
+weight: 3
 ---
 
 In the bottom pane is where any related content will be reported. In the screenshot below you can see that APM has found a trace that is related to this log line **(1)**:
 
 ![RC](../../images/log-apm-rc.png)
 
-By clicking on **Trace for 0c5b37a751e1fc3e7a7191140ex714a0** **(2)** will take us to the waterfall in APM for this specific trace that this log line was generated from:
+By clicking on **Trace for 4be8b620a98aa938e76cf76aa1bde396** **(2)** will take us to the waterfall in APM for this specific trace that this log line was generated from:
 
 ![waterfall logs](../../images/waterfall-with-logs.png)
 
-Note that you now have Related Content pane  for Logs appear **(1)**. Clicking on this will take you back to Log Observer and will display all the log lines that are part of this trace.
+Note that you now have Related Content pane for Logs appear **(1)**. Clicking on this will take you back to Log Observer and will display all the log lines that are part of this trace.

content/en/other/3-automatic-discovery/2-petclinic-kubernetes/7-log-observer-connect/1-configure-logback.md

@@ -2,6 +2,7 @@
 title: Deploy to Kubernetes
 linkTitle: 3. Deploy to Kubernetes
 weight: 3
+hidden: true
 ---
 
 To see the changes in effect, we need to redeploy the services, First, let's change the location of the images from the external repo to the local one by running the following script: