[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opennms-buglist
Subject:    [Buglist] [Bug 2559] New: Request for a functionality to go shopping for graphs
From:       bugzilla () opennms ! org (bugzilla at opennms ! org)
Date:       2008-06-26 8:03:01
Message-ID: bug-2559-627 () http ! bugzilla ! opennms ! org/
[Download RAW message or body]

http://bugzilla.opennms.org/show_bug.cgi?id=2559

           Summary: Request for a functionality to go shopping for graphs
           Product: OpenNMS
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P1
         Component: webUI - General
        AssignedTo: buglist at opennms.org
        ReportedBy: af at syd.de


Situation:
I am currently analyzing ex post the behaviour of a system. To do so I need to
understand what has happened at what time in the system landscape.
For static problems I would create a ksc report.
My problems change however _and_ the configuration process for ksc reports is
quite static (you need to know what you want to know).

Idea:
It would be cool if I could go "shopping for graphs": When I browse Amazon, I
look through the catalog and drop items off into my shopping basket. When
finished I have all the items in my basket, can remove them and pay for all or
a selection.
The workflow used is "browse and drop, look at your results later".
Related to OpenNMS this could mean that while exploring graphs you'd have an
option to "earmark" them (or put them in a basket).
When finished (or when you feel like) you go to your "basket" and see all the
graphs selected in a timely context (eg all for the same time span).

Does it make sense?

For me - yes. I have a graph which shows the numbers of transactions processed
on systems (and the total system). It's very useful to be able to relate
results in graphs to the number of users to understand if problems are rather
load related or might be located in a different area.

The technical implementation could probably end up using the existing KSC
reports, just with another configuration facility.


-- 
Configure bugmail: http://bugzilla.opennms.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[prev in list] [next in list] [prev in thread] [next in thread]