Skip to content

Commit 0fce710

Browse files
committed
Update README.md of Challenge 1
1 parent 702ac6e commit 0fce710

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

challenge-01/README.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -11,13 +11,11 @@ The goal is to have fun and learn in the first place.
1111
> 🚨 **Challenge**:
1212
> - Run the sample application
1313
> - Run the tests to see what happens
14-
> - Try to find out what is happens, make a hypothesis❗
14+
> - Try to find out what happens, make a hypothesis❗
1515
> - **Improve the observability** of the application to **prove the hypothesis**
1616
> - Optional: fix the problem and **prove it with observability data that it is really fixed**
1717
> - Optional, but highly appreciated 🙏: Share your findings, insights you learned and potential solution, either as a ['discussion'](https://github.com/cbos/application-observability-code-challenges/discussions) or as a pull request
1818
19-
In one or two weeks I will come up with a blogpost with insights, observability improvements and possible solutions.
20-
2119
An online guided environment is available with KillerCode, see [https://killercoda.com/observability-code-challenges](https://goto.ceesbos.nl/aocckk)
2220

2321
## Challenge
@@ -50,7 +48,7 @@ cd application-observability-code-challenges/challenge-01
5048
```shell
5149
just download-otel
5250
```
53-
This download the OpenTelemetry Java agent jar to the `.otel` directory.
51+
This downloads the OpenTelemetry Java agent jar to the `.otel` directory.
5452

5553
### Build the application
5654

@@ -59,9 +57,9 @@ just build
5957
# or if you want to do it manually
6058
./mvnw clean verify
6159
```
62-
This will download the OpenTelemetry Java agent jar into the `.otel' directory.
60+
This will build and package the application.
6361

64-
### Observability Tooklit or your own stack
62+
### Observability Toolkit or your own stack
6563
Launch your observability stack or use the Observability Toolkit.
6664
The sample application assumes that you have an OpenTelemetry endpoint running at `localhost:4318`.
6765

@@ -219,7 +217,7 @@ just k6-with-heavy-query
219217
```
220218
221219
This is not a complicated test, but a test to see what happens when a 'heavy' query is executed.
222-
Suddenly all queries will hang, it is like you customers complaining about a slow system 🚨.
220+
Suddenly all queries will hang, it is like your customers complaining about a slow system 🚨.
223221
![Slow responses](images/k6_slow_responses.png)
224222
225223
# Observability improvements hints

0 commit comments

Comments
 (0)