<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=594205) </details> <!--IssueSummary end--> ## Goal Create an example of what can be achieved by creating proper monitoring over a feature flag ## How - Create an endpoint in GitLab api called `/chaos`. This endpoint is only accessible by employees - Create a feature flag called `ebonet_chaos_tests` - When a user hits the `/chaos` endpoint, the feature flag is tested against a random project - If the feature flag is enabled, in 20% of the cases the request will fail, and in 20% of the cases it will add .3s to the processing time. - If the feature flag is disabled, nothing happens Once the feature flag is activated, perform a 1000 requests spaced by 0.5 each. Create a kibana dashboard that shows the comparison of the feature flag, when it is on and when it is off