Page MenuHomeSoftware Heritage

add end-to-end icinga check(s) that graph objects are browsable via the Web UI
Closed, MigratedEdits Locked

Description

It has happened in the past that some objects from the archive were not accessible via the Web UI (e.g., contents due to the object storage not being available, but of course any other reason might happen).
We should add end-to-end incinga checks that via the Web interface (i.e., checking the HTML in horrible ways) we can access various kind of objects.
One object per type sounds like the right way to go:

  • content
  • directory
  • revision
  • release
  • snapshot

Event Timeline

zack triaged this task as Normal priority.May 30 2018, 3:44 PM
zack created this task.
zack moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

@anlambert can you post here one example per object-type that we can use for this task?

For each object type we need the object ID and a reasonably stable string that comes from its content and that we are guaranteed to find in the HTML body.
TIA!

Below is some examples of endpoints and expected string to be found in HTML:

zack changed the task status from Open to Work in Progress.Jun 12 2018, 6:46 PM
zack updated the task description. (Show Details)
zack updated the task description. (Show Details)