I noticed that you used image height param format as the font size.
https://github.com/Belval/TextRecognitionDataGenerator/blob/33d8985521645280e102987e773bf1e424a045df/TextRecognitionDataGenerator/computer_text_generator.py#L14
In my test, image_font = ImageFont.truetype(font=font_size=500), no error was reported, but it was time consuming.
So I am confused, why set format, font_size

1 - (sum(count_over_time(kuberhealthy_check{check="kuberhealthy/deployment", status="0"}[30d])))/(sum(count_over_time(kuberhealthy_check{check="kuberhealthy/deployment", status="1"}[30d])) * 100)

This query makes it possible to formulate a 30 day uptime percentage. We should document this for our users so that they can use it with their own synthetic checks easily. It would be good

There are a number of complex parameters for outcome simulations. These need to be documented, validated, and examples need to be given for how the user can adjust them.

Suggested values should be documented. And each parameter should be described so users expect what it does.

We should make sure that the pipeline throws an error if a config option / parameter is passed to a stage which is not requested.