Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,13 @@ For the Splunk Log Observer component, the Splunk OpenTelemetry Collector automa

Log Observer provides a real-time view of logs from your applications and infrastructure. It allows you to search, filter, and analyze logs to troubleshoot issues and monitor your environment.

Go back to the PetClinic web application and click on the **Error** link several times. This will generate some log messages in the PetClinic application logs.
Go back to the PetClinic web application in your web browser and click on the **Error** link several times. This will generate some log messages in the PetClinic application logs.

![PetClinic Error](../images/petclinic-error.png)

From the left-hand menu click on **Log Observer** and ensure **Index** is set to **splunk4rookies-workshop**.
From the Splunk Observability Cloud left-hand menu, click on **Logs → Log Observer** and ensure **Index** is set to **splunk4rookies-workshop**.

Next, click **Add Filter** search for the field `service.name` select the value `<INSTANCE>-petclinic-service` and click `=` (include). You should now see only the log messages from your PetClinic application.
Next, click **Add Filter**, search for the field `service.name`, select the value `<INSTANCE>-petclinic-service` and click `=` (include). Click **Run search**. You should now see only the log messages from your PetClinic application.

Select one of the log entries that were generated by clicking on the **Error** link in the PetClinic application. You will see the log message and the trace metadata that was automatically injected into the log message. Also, you will notice that Related Content is available for APM and Infrastructure.

Expand Down