Mathieu Leplatre

Good point, but I think it's fine if we check it like on the login page when fetching capabilities, and then maybe once every minute or so. We also have...

I'm looking at the startup: https://github.com/mozilla-services/telescope/blob/d22e1e1f14e5945f951ea9e3588a1d97d47fefcc/telescope/__main__.py#L6 https://github.com/mozilla-services/telescope/blob/ec60106f80fe60a9da98c93b5341abc522c5dd94/telescope/app.py#L493 And it does not seem to execute any check.

According to Dustin, the order of the list of containers does not have any major impact, so https://github.com/mozilla-it/webservices-infra/pull/3108 was probably the reason it got fixed. However, since we were allowing...

Situation observed yesterday. Was green after refresh.

I tried to simulate a slow server with: ``` docker run --publish 0.0.0.0:8888:8888 alpine nc -lk -p 8888 -e sleep 60s ``` ([source](https://carltonhenderson.github.io/simulating-slow-http-servers/)) Using: ```toml [checks.test.hb] description = "" module...

Something to take into account: should we publish our curl container instead of rebuilding it each time?

What would be the input to generate the diagram?

There are different ways to achieve this. Adding views to a single instance, or run multiple instances. Since running Poucave is pretty cheap, I would have a preference for the...

> If we can make the setup/deployment process as easy as adding/updating a configuration we could keep poucave simple (+1) and still get custom pages. I agree. Let's see, concretely...

How many and how often do you think we'd have to create new pages? Things to consider: - drawing a SVG is a piece of cake - creating a `config.toml`...