Skip to content

Commit 5d67a52

Browse files
committed
Merge remote-tracking branch 'upstream/main'
2 parents d512db3 + f7174c0 commit 5d67a52

File tree

4 files changed

+32
-4
lines changed

4 files changed

+32
-4
lines changed

content/en/ninja-workshops/8-docker-k8s-otel/2-deploy-collector.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -105,6 +105,8 @@ for further details on how to install the collector.
105105

106106
Let's confirm that the collector is running successfully on our instance.
107107

108+
> Press Ctrl + C to exit out of the status command.
109+
108110
{{< tabs >}}
109111
{{% tab title="Script" %}}
110112

@@ -137,6 +139,8 @@ sudo systemctl status splunk-otel-collector
137139

138140
We can view the collector logs using `journalctl`:
139141

142+
> Press Ctrl + C to exit out of tailing the log.
143+
140144
{{< tabs >}}
141145
{{% tab title="Script" %}}
142146

content/en/ninja-workshops/8-docker-k8s-otel/3-deploy-dotnet-app.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -144,7 +144,7 @@ info: Microsoft.Hosting.Lifetime[0]
144144
{{% /tab %}}
145145
{{< /tabs >}}
146146

147-
Once it's running, open a second SSH terminal and access the application using curl:
147+
Once it's running, open a second SSH terminal to your Ubuntu instance and access the application using curl:
148148

149149
{{< tabs >}}
150150
{{% tab title="Script" %}}
@@ -182,6 +182,8 @@ Hello, Tom!
182182
{{% /tab %}}
183183
{{< /tabs >}}
184184

185+
> Press Ctrl + C to quit your Helloworld app before moving to the next step.
186+
185187
## Next Steps
186188

187189
What are the two methods that we can use to instrument our application with OpenTelemetry?

content/en/ninja-workshops/8-docker-k8s-otel/4-instrument-app-with-otel.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -183,4 +183,6 @@ Next, click on **Traces** on the right-hand side to see the traces captured for
183183

184184
An individual trace should look like the following:
185185

186-
![Traces](../images/trace.png)
186+
![Traces](../images/trace.png)
187+
188+
> Press Ctrl + C to quit your Helloworld app before moving to the next step.

content/en/ninja-workshops/8-docker-k8s-otel/5-dockerize-app.md

Lines changed: 22 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -45,9 +45,20 @@ instructions to the image builder on the commands to run, files to copy, startup
4545

4646
## Create a Dockerfile
4747

48-
Let's create a file named `Dockerfile` in the `/home/splunk/workshop/docker-k8s-otel/helloworld` directory.
48+
Let's create a file named `Dockerfile` in the `/home/splunk/workshop/docker-k8s-otel/helloworld` directory.
4949

50-
It should include the following content:
50+
``` bash
51+
cd /home/splunk/workshop/docker-k8s-otel/helloworld
52+
```
53+
54+
You can use vi or nano to create the file. We will show an example using vi:
55+
56+
``` bash
57+
vi Dockerfile
58+
```
59+
Copy and paste the following content into the newly opened file:
60+
61+
> Press 'i' to enter into insert mode in vi before pasting the text below.
5162
5263
``` dockerfile
5364
FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base
@@ -75,6 +86,15 @@ COPY --from=publish /app/publish .
7586
ENTRYPOINT ["dotnet", "helloworld.dll"]
7687
```
7788

89+
To save your changes in vi, hit the ESC key then type
90+
91+
``` bash
92+
:wq!
93+
94+
```
95+
followed by the ENTER/RETURN key.
96+
97+
7898
What does all this mean? Let's break it down.
7999

80100
## Walking through the Dockerfile

0 commit comments

Comments
 (0)