[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] Graph Limits
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] Graph Limits
- From: Henrik Stoerner <henrik (at) hswn.dk>
- Date: Wed, 2 Feb 2005 07:47:32 +0100
- References: <20050126222913.GB11218@hswn.dk> <41F9C377.4070302@cisco.com> <41F9CB61.7050109@cisco.com> <20050128092542.GA29457@hswn.dk> <41FA0D88.4000900@cisco.com> <41FA0E97.5070401@cisco.com> <20050128112203.GA31554@hswn.dk> <41FA264F.1040806@cisco.com> <20050128133939.GC1295@hswn.dk> <42001A7E.1030907@cisco.com>
- User-agent: Mutt/1.5.5.1i
On Tue, Feb 01, 2005 at 05:10:38PM -0700, Charles Jones wrote:
> Sometimes a large spike can ruin a graph, because the graph then scales
> to the max size of the spike, so the rest of the graph isn't very
> readable as it is now scrunched down to almost a flat line. Is it
> possible to have an option for Hobbits larrding so that you can define a
> maximum threshold not to extend past?
Yes, but it's actually a feature that exists in RRDtool, which is used
to generate the graphs. Just change hobbitgraph.cfg's [la] definition:
[la]
... some lines ...
CDEF:la=avg,100,/
--upper-limit 3.0
--rigid
.... more lines ...
The --upper-limit sets the value for the top of the graph; the --rigid
makes this setting "rigid" so even if there are larger values in the
dataset, the graph will not adapt to show these.
It might be an idea to let this upper value be determined by the CGI
so you can adjust it dynamically. I'll have a look at that.
Henrik