Change Details

There remains currently 2 checks which returns 404 on icinga. It's happening because we recently started back from scratch the staging archive (then migrated on new storage1/db1) We now need to find back all the origins to ingest in that archive so those get green again. We could also make the checks more dynamic somehow.

There remains currently 2 checks [1] [2] which returns 404 on icinga. It's happening because we recently started back from scratch the staging archive (then migrated on new storage1/db1) We now need to find back all the origins to ingest in that archive so those get green again. We could also make the checks more dynamic somehow. [1] https://icinga.softwareheritage.org/dashboard#!/monitoring/service/show?host=webapp.internal.staging.swh.network&service=swh%20webapp%20revision%20log%20end%20to%20end [2] https://icinga.softwareheritage.org/monitoring/list/services?service_problem=1&sort=service_severity&dir=desc#!/monitoring/service/show?host=webapp.internal.staging.swh.network&service=swh%20webapp%20snapshot%20end%20to%20end

There remains currently 2 checks [1] [2] which returns 404 on icinga. It's happening because we recently started back from scratch the staging archive (then migrated on new storage1/db1) We now need to find back all the origins to ingest in that archive so those get green again. We could also make the checks more dynamic somehow. [1] https://icinga.softwareheritage.org/dashboard#!/monitoring/service/show?host=webapp.internal.staging.swh.network&service=swh%20webapp%20revision%20log%20end%20to%20end [2] https://icinga.softwareheritage.org/monitoring/list/services?service_problem=1&sort=service_severity&dir=desc#!/monitoring/service/show?host=webapp.internal.staging.swh.network&service=swh%20webapp%20snapshot%20end%20to%20end