Red Hat Bugzilla – Bug 534711
Have Events tab show up only when the resource type supports events
Last modified: 2015-02-01 18:25:05 EST
Right now the Event tab shows up between Monitor and Inventory on every resource regardless of whether that resource generates events or not. This is the opposite to how the other tabs work, e.g. Content, Operations, which only appear when the type of the resource supports that feature.
the Events tab is how you also get to the timeline - and that should be visible for all resources (since it shows alerts, config changes, avail changes, etc)
mazz, true, though maybe the timeline stuff shouldn't be in the events tab. maybe it needs it's own tab altogether since it cross availability, events, operations, alerts, etc
all the tabs today represent distinct subsystems (Operations, Monitoring, Alerts, Configuration, etc).
The timeline doesn't really fit into the category of a "subsystem" - its a place where all the subsystems aggregate their information into one view. Its kinda like the "subsystems" view, but across a single resource, not the entire inventory.
So, I don't think timeline should be on its own tab, but I don't know where it should go :)
the monitor tab has monitoring data, but it also has availability as well as events
the alerts tab has alerts as well as the operations that were triggered as part of an alert being fired
rev3054 - the 'e' icon will only show up for resources that support events, or compatible groups containing resources that support it;
where is the link to the timeline now?
i'm willing to put it anywhere that makes sense. i'm leaning towards making it into it's own tab -- thoughts?
That would be ok, but give yet another icon ... But now that the TL works :) OTOH If Events is only the history then, we can put it back under Monitor.
since its an aggregation of all the other subsystems, I would think it makes the most sense as a tab inside the subsystems page
see the screenshot from the linked jira.
Only see events tab for supported resource types. rev3238
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1481
This bug relates to RHQ-1575