Hi,
The ABRT team had an idea - ABRT can catch problems from containers and ABRT displays
problems in Cockpit. So why not to show problems that happened in containers directly
under container overview?
Here I have a short user story for you (inspired by existing one):
Robert Paulsson is a developer at a small IT company. He's a senior engineer, but got
tossed the sysadmin hat at the company. The company have 3 internal servers that runs
various services that the R&D unit needs for their day to day basis. He is responsible
for these servers and services that are running on them.
Robert logs into the system via Cockpit and goes to the containers page. (version 1. - He
immediately sees that something is wrong with running container (there is exclamation
mark, see below), so he opens it to learn more.) (version 2. His colleagues brought to his
notice, that they are not able to connect to one internal instance of their product. He
knows in which container this instance is running, so he opens it to learn more.) He
notices 'Problems' tab, opens it and sees that there is some problem. Clicks on it
and is redirected into ABRT journal log. After reporting he finds out that the issue is
known. He is able to fix this issue.
How it could work:
(navigate to Containers)
Open some container with the dropdown on the left of container name.
You should see container details. Our idea was to add another tab 'Problems' next
to details. It should contain list of all problems that occurred in that container.
https://ibb.co/ePxerv (something like this)
Each item should be clickable and redirect into logs.
Maybe it would be nice to display some exclamation mark next to state in the default
container view (before dropdown-ing it).
https://ibb.co/fU7qya (something like this)
What do you think of this? Does it sound like a good idea? (The mock-ups are only for
better understanding. Definitely I would like to see design from you)
All the best,
Matt Marusak
ABRT team