Hello Cockpit crew,
I am working on ABRT and I am the author of the 'org.freedesktop.Problems' support idea [1].
I would like to let you that we have developed a Cockpit module [2] showing problems detected by ABRT and allowing users to report them. The module is still rather a proof of concept (especially the reporting part) but we wanted to make you aware of its existence.
I have prepared a demonstration video: https://plus.google.com/106984072939419636032/posts/C95w9HZWCh6
and a Fedora COPR with the packages: https://copr.fedorainfracloud.org/coprs/jfilak/cockpit-abrt-devel/
I know Cockpit development is driven by user stories but I didn't want to write a hypothetical case. Last week I got a lot of luck, because I found a crash of realmd [3] which was reproducible using Cockpit. So, here is our user story:
Charles King, an administrator at Czechlands, wants to add John's work station to Romanum Active Directory Domain. Charles logs in to Cockpit on John's work station, clicks the 'Join Domain' button, fills in required information and hits return. After a while, "Message recipient disconnected from message bus without replying" error message appears. Charles tries to sort out the problem so he looks into the system logs and discovers a message about realmd crash. He opens "Tools" menu and goes to "Problems" item where he finds an entry for the crash. He reviews the data presented and decides to report the problem. The report reply includes a link to a Bugzilla bug which is already fixed. Charles updates John's box and successfully adds the box to Romanum domain.
The module uses some experimental work and it is definitely not production ready. However, we would love to hear any feedback from you before we spend too much time doing wrong things.
Kind regards, Jakub ABRT
1: https://github.com/cockpit-project/cockpit/wiki/Ideas 2: https://github.com/abrt/cockpit-abrt/tree/problems2 3: https://bugzilla.redhat.com/show_bug.cgi?id=1330766
On 27.05.2016 13:17, Jakub Filak wrote:
Hello Cockpit crew,
I am working on ABRT and I am the author of the 'org.freedesktop.Problems' support idea [1].
I would like to let you that we have developed a Cockpit module [2] showing problems detected by ABRT and allowing users to report them. The module is still rather a proof of concept (especially the reporting part) but we wanted to make you aware of its existence.
I have prepared a demonstration video: https://plus.google.com/106984072939419636032/posts/C95w9HZWCh6
and a Fedora COPR with the packages: https://copr.fedorainfracloud.org/coprs/jfilak/cockpit-abrt-devel/
I know Cockpit development is driven by user stories but I didn't want to write a hypothetical case. Last week I got a lot of luck, because I found a crash of realmd [3] which was reproducible using Cockpit. So, here is our user story:
Charles King, an administrator at Czechlands, wants to add John's work station to Romanum Active Directory Domain. Charles logs in to Cockpit on John's work station, clicks the 'Join Domain' button, fills in required information and hits return. After a while, "Message recipient disconnected from message bus without replying" error message appears. Charles tries to sort out the problem so he looks into the system logs and discovers a message about realmd crash. He opens "Tools" menu and goes to "Problems" item where he finds an entry for the crash. He reviews the data presented and decides to report the problem. The report reply includes a link to a Bugzilla bug which is already fixed. Charles updates John's box and successfully adds the box to Romanum domain.The module uses some experimental work and it is definitely not production ready. However, we would love to hear any feedback from you before we spend too much time doing wrong things.
This is pretty cool.
Thinking about the integration here a bit ...
Is there a relevant journal entry we can use to generate links to the problems in question? It would be cool to perculate this up into a troubleshooting page and we've planned to use the journal and message catalogs to do that:
https://www.freedesktop.org/wiki/Software/systemd/catalog/
If there was a relevant journal entry that had a catalog message id, we could handle that specially and allow the user to click through to the Problem, and perform the actions in the video. What do you think?
Stef
On 06/01/2016 04:49 PM, Stef Walter wrote:
On 27.05.2016 13:17, Jakub Filak wrote:
The module uses some experimental work and it is definitely not production ready. However, we would love to hear any feedback from you before we spend too much time doing wrong things.
This is pretty cool.
Thinking about the integration here a bit ...
Is there a relevant journal entry we can use to generate links to the problems in question? It would be cool to perculate this up into a troubleshooting page and we've planned to use the journal and message catalogs to do that:
https://www.freedesktop.org/wiki/Software/systemd/catalog/
If there was a relevant journal entry that had a catalog message id, we could handle that specially and allow the user to click through to the Problem, and perform the actions in the video. What do you think?
I was thinking about integration too.
ABRT logs several messages when a new problem (coredump, python exception, koops, ...) is detect but none of those has MESSAGE_ID. However, we have been thinking about improvements in ABRT logging for quite a long while and one of our goals is to write a "valuable" error message to systemd-journal, so I will look into it now.
Do you have any hints/tips/wishes on how you would want the message be composed?
Jakub
On 02.06.2016 12:33, Jakub Filak wrote:
On 06/01/2016 04:49 PM, Stef Walter wrote:
On 27.05.2016 13:17, Jakub Filak wrote:
The module uses some experimental work and it is definitely not production ready. However, we would love to hear any feedback from you before we spend too much time doing wrong things.
This is pretty cool.
Thinking about the integration here a bit ...
Is there a relevant journal entry we can use to generate links to the problems in question? It would be cool to perculate this up into a troubleshooting page and we've planned to use the journal and message catalogs to do that:
https://www.freedesktop.org/wiki/Software/systemd/catalog/
If there was a relevant journal entry that had a catalog message id, we could handle that specially and allow the user to click through to the Problem, and perform the actions in the video. What do you think?
I was thinking about integration too.
ABRT logs several messages when a new problem (coredump, python exception, koops, ...) is detect but none of those has MESSAGE_ID. However, we have been thinking about improvements in ABRT logging for quite a long while and one of our goals is to write a "valuable" error message to systemd-journal, so I will look into it now.
Do you have any hints/tips/wishes on how you would want the message be composed?
Great. As I understand it, having a MESSAGE_ID (which is a GUID) present on a key message that describes the fact that the "Problem" occurred. This could be added to one or more of the messages you described if you don't have a single message that covers all the cases.
That's what we planned out during a discussion at DevConf hackfest: Providing specific UI per "troubleshootable" issue, and then using a query against the journal to pull up all the various issues, and mapping them to the specific UI by GUID.
Stef
cockpit-devel@lists.fedorahosted.org
-
Jakub Filak -
Stef Walter