We should add a check that uses one of our endpoint usage examples (e.g., https://archive.softwareheritage.org/api/1/content/adc83b19e793491b1c6ea0fd8b46cd9f32e592fc/ ) and verifies it returns meaningful data fetched from the DB (e.g., one of its other checksums, like 01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b).

Caveat: as we stand, icinga is going to hit the rate limit, so we need to first whitelist the IP icinga is coming from (or all local IPs, maybe).