Skip to content
This repository has been archived by the owner on Jul 23, 2022. It is now read-only.

Introduce an Issue/Emergency Scenario during the monitoring #354

Open
gsampaio-rh opened this issue Jul 11, 2019 · 1 comment
Open

Introduce an Issue/Emergency Scenario during the monitoring #354

gsampaio-rh opened this issue Jul 11, 2019 · 1 comment
Labels
enhancement New feature or request need more info

Comments

@gsampaio-rh
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Some attendees asked about real user cases scenarios that we can share/present during DO500. The request comes from the perspective that they want us to share situations that we experienced and how they got addressed (What's already included in our KitBags) but maybe that's an opportunity to introduce an application monitoring/logging/observability exercise in chapter 16.

Describe the solution you'd like
We can "break" the team's applications and purpose them to find the problem so they can experience an issue situation. This will give an opportunity to check traceability, logging and maybe we can use that as an opportunity to implement monitors, or just liveness and readiness probes, in the application.

Describe alternatives you've considered
As this is not a mandatory exercise would be more a question if we have time on the final day to run this practice or just go over the slides.

@tdbeattie tdbeattie added this to the Add More Tech Content milestone Jul 29, 2019
@springdo
Copy link
Contributor

would like to see this as an exercise! looking forward to your PR :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request need more info
Projects
None yet
Development

No branches or pull requests

4 participants