Skip to content

Commit

Permalink
Draft post of the first challenge
Browse files Browse the repository at this point in the history
  • Loading branch information
cbos committed Jan 15, 2025
1 parent e63cc82 commit 055cb75
Show file tree
Hide file tree
Showing 5 changed files with 66 additions and 0 deletions.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
66 changes: 66 additions & 0 deletions content/posts/20250116-first-observability-code-challange/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
---
title: "Application Observability Code Challenge 1"
date: 2025-01-15T12:44:23Z
pin: true
draft: true

resources:
- src: "**.{png,jpg,webp}"
title: "Image #:counter"

tags:
- Grafana
- Observability
- OpenTelemetry
- AOCC
- Java

slug: aocc-challenge-01

summary:
The first of the Application Observability Code Challenges is now available. A simple Spring Boot application with a REST endpoint implemented in Jersey/JAX-RS
This application has some unexpected behaviour. Can you find out what is happening based on the observability data? Can you improve the observability to prove that a fix really fixed the problems?
---

![Application Observability Code Challenge 1](aocc_challenge01_small.png)

The first challenge of the Application Observability Code Challenges is now available.
See the [announcement blog](../application-observability-code-challenges) for more information about the challanges in general.
The goal is to have fun and learn in the first place.

> 🚨 **Challenge**:
> - Run the sample application
> - Run the tests to see what happens
> - Try to find out what is happens, make a hypothesis❗
> - **Improve the observability** of the application to **prove the hypothesis**
> - Optional: fix the problem and **prove it with observability data that it is really fixed**
> - 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
### Run local or with an online environment
All details of the challenge are available at [https://github.com/cbos/application-observability-code-challenges/tree/main/challenge-01](https://goto.ceesbos.nl/ghch01)
An online guided environment is available with KillerCode, see [https://killercoda.com/observability-code-challenges](https://goto.ceesbos.nl/aocckk)

### Challenge details

- The sample application is a simple Spring Boot application with a REST endpoint implemented in Jersey/JAX-RS.
- The application is instrumented using OpenTelemetry auto instrumentation.
- You can either run the application with Docker or directly.
- K6 load scripts are prepared to run tests that provide more insight into the issues.

The setup looks like this:
![Setup](k6_application_setup.png)

After running one of the scripts you can get more details in a Grafana dashboard like this:
![K6 dashboard](k6_highload_dashboard.png)

In this screenshot you can see that the application is reaching a limit for some reason, more load does not give more requests per second and with more load the response times increase a lot.

Go to the challenge: [https://github.com/cbos/application-observability-code-challenges/tree/main/challenge-01](https://goto.ceesbos.nl/ghch01)

### Feedback?

If you have any feedback, please let me know. You can leave a comment below, send me a message on Bluesky, Mastodon, LinkedIn or in the ['discussion'](https://github.com/cbos/application-observability-code-challenges/discussions) section of the challenge's Github repository .




Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

0 comments on commit 055cb75

Please sign in to comment.