operations-portal-users » ROD-DASHBOARD

Hi,

See https://ggus.eu/index.php?mode=ticket_info&ticket_id=106149 for an example.

What does the text of the original ticket tell me?

timestamp: good
test_name: pretty much worthless
host_name: good
service: ok
status: ok, but ...

URL_to_history takes me somewhere that is potentially interesting, but the name is bad.

The ticket lacks important information; if a user submitted this ticket, I would reply with "please provide the following information". An automated system should provide better reports than a user -- the automated system presumably knows much better than a user what information is important to include.

So please ensure that in the future, the ROD-dashboard-submitted tickets includes this information. Not doing so is making a joke out of EGI -- the main function of the tool as it is now, is to save effort at the operations end. The primary function should however be to save effort for the (much larger) group of site admins, these tickets fail in this regard.

Information that should be included in the ticket.

- a link to the documentation for the SPECIFIC TEST that has failed. what is now provided is a link to a long list of tests, creating work for the admin -- she needs to find the test name and then search for it on a different page

- the exact command that failed, and the output (or lack of output) that signals that this command was not successful.

In other words, the ticket should contain enough information that I do not need to click any other links in order to understand the result and error.

An acceptable alternative is to have the page include a direct (direct means 1 single click) link to the failed test itself, showing the exact command attempted, output returned, and clear markup of the point at which failure was identified.

Thanks!