Thanks for your opinions. A few things are coming out of this:
1) Keep the old /rrdgraph url which draws the old images. We plan on
leaving these in, though obviously future development is based on the
new javascript page. We have test scripts that check that /rrdgraph
will still return image files, so it should still remain in future
releases
2) Keep the old /graph. We moved the old /graph into /graphrrd for
testing purposes. This is likely to be removed in future. At best, we
may leave it in but it may well break with future UI changes
3) The times are in UTC only. I don't know how we missed this, but
that's a bug and we'll get that fixed for 3.5.1. If it is a simple
fix, I'll post a link to the patch.
Other replies inline....
On 2 Dec 2009, at 05:59, David LaPorte wrote:
I love the new graphing system. It's so much easier to get more
meaningful information out of the graphs rather than having everything
averaged into oblivion once you get past a day unless you have very
gradual value changes.
As the backend is still RRD, the averaging will still happen. You'll
need ODW if you want raw data.
I agree that it's much harder to integrate the generated graphs into
other applications, though. You'd have to write your own scripts to
generate images for you from the RRDs which isn't a big deal but it's
a lot more work than none. :)
We did provide embed options though haven't tried it in earnest
ourselves yet. That's meant to embed the graph in other pages.
I also feel like the drag-zoom selector isn't very accurate.
Sometimes I have to try a few times to figure out what I actually need
to hilite to get the information I'm interested in. The panning
doesn't work very well either. Both work great in FireFox. But not
in IE or Safari which are the only other browsers that I have tried.
We have tested in IE7/8 and Safari. Is the "snap to now" option on?
That affects the zooming.
On Nov 27, 2009, at 1:48 AM, Kang wrote:
it's lack of customizable options compare to old rrdgraph( upper/
lower limit, static cur/min/max legend label, fast static image
rendering, etc.)
We chose to put the cur/min/max as a hover over because it just took
up too much graph space. I guess a separate table might be the other
place for this type of information.
What do you mean by upper/lower limit? I think there are some possible
optimisations with how the graphs choose the top and bottom values for
the y-axis.
Ton
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users
