Jesse Becker wrote:
On Wed, Jan 6, 2010 at 12:01, Ofer Inbar c...@a.org wrote:
Daniel Pocock dan...@pocock.com.au wrote:
and 3.2 can possibly go to a full XML format gmetad.conf with more
advanced templates, etc.
Please tell me that's not being considered?
XML is a
Daniel Pocock wrote:
- is it important for users to maintain the files manually, or will the
focus shift to tools, web interface or config files generated from some
other enterprise data source?
I've been content with the existing file format for the 7 or so years
I've been running
Carlo Marcelo Arenas Belon wrote:
On Mon, Jan 04, 2010 at 06:55:36AM -0500, Jesse Becker wrote:
On Mon, Jan 4, 2010 at 03:46, Carlo Marcelo Arenas Belon
care...@sajinet.com.pe wrote:
My goal is to allow different sets of RRAs for different sources, while
making sure the existing
On Wed, Jan 6, 2010 at 12:01, Ofer Inbar c...@a.org wrote:
Daniel Pocock dan...@pocock.com.au wrote:
and 3.2 can possibly go to a full XML format gmetad.conf with more
advanced templates, etc.
Please tell me that's not being considered?
XML is a horrible lousy format for these kinds of
On Mon, Dec 28, 2009 at 10:16:28PM +, Daniel Pocock wrote:
I'm looking at extending the gmetad.conf format, while still making sure
that it can read the existing config files.
adding a new configuration option would be the easiest way to prevent
any backward incompatible change which
On Mon, Jan 4, 2010 at 03:46, Carlo Marcelo Arenas Belon
care...@sajinet.com.pe wrote:
My goal is to allow different sets of RRAs for different sources, while
making sure the existing file format remains valid.
why do you want to have this? what is the use case for having different
metric
On Mon, Jan 04, 2010 at 06:55:36AM -0500, Jesse Becker wrote:
On Mon, Jan 4, 2010 at 03:46, Carlo Marcelo Arenas Belon
care...@sajinet.com.pe wrote:
My goal is to allow different sets of RRAs for different sources, while
making sure the existing file format remains valid.
why do you want
I'm definitely in favor of the pattern-oriented designs, and I do
agree this is really great idea. I'm more interested in changing the
RRAs per-metric than per-source, so any solution that only solved the
per-source part of the problem would be less good.
The script or callback solution
I'm looking at extending the gmetad.conf format, while still making sure
that it can read the existing config files.
There are two particular lines that interest me:
RRAs RRA:AVERAGE:0.5:1:244 RRA:AVERAGE:0.5:24:244
RRA:AVERAGE:0.5:168:244 RRA:AVERAGE:0.5:672:244 \
A few random thoughts inline below.
Regardless of the specifics, I think this is a really great idea.
On Mon, Dec 28, 2009 at 17:16, Daniel Pocock dan...@pocock.com.au wrote:
I'm looking at extending the gmetad.conf format, while still making sure
that it can read the existing config files.
10 matches
Mail list logo
