Bug 207394
| Summary: | Observer creation UI seems to be backwards for common cases. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dave Malcolm <dmalcolm> |
| Component: | frysk | Assignee: | Andrew Cagney <cagney> |
| Status: | CLOSED UPSTREAM | QA Contact: | Len DiMaggio <ldimaggi> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rawhide | CC: | mcvet, mjw, npremji, pmuldoon, rmoseley, scox, timoore, triage |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | bzcl34nup | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2008-04-09 20:40:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Dave Malcolm
2006-09-20 22:06:25 UTC
Actually Program Obvservers are orthogonal to watching processes for events. In fact, they will be removed and refactored to me be more in line with the workflow. Point well taken there. The workflow for watching a process or a task is: - Create a session with the session manager. This is the first UI you will see. From there you can create a session that allows you to add processes, tasks, observers and so on. - Launch that session I'm curious as to how you got to the actual process monitor before going through these steps, which setup your environment to detail your points above. Also, you can add additional observers by right clicking on the process or task, and click Add Observer -> select your observer. Custom observers are a different feature altogether, allowing you to customize your actions and filters on observe rfire (say fork). They allow you to further refine the base observers. I see two action items here. Remove program observers in thier current context. They are confusing and lead people away from the workflow. Make sure the user goes through the "setup a session druid" before allowing you to go to the monitor. Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again. The whole observer and monitoring support in the gui has been redesigned since this bug was opened. A couple of the suggestions in comment #2 have been adopted. Please review the current gui and open a new bug upstream for any additional issues you see. (Disclaimer, the frysk gui and monitoring has been deemphasized upstream to focus on debugging and core tools/cli support first). |