Re: [Perfparse-devel] Submitting work

[Yves M. <yme...@li...>]

> Hi,
>
> I saw my name mentioned eight times, let me add to this discussion :)

Respect to our leader :)

> I totally agree about submitting patches.  There is a facility to do
> this on http://perfparse.sf.net.  I have not used this, but this might
> guarantee all of us can see the patch and gives you somewhere to post
> it.  If there are more than a few of us, might be time to us it.

OK, so I will apply the patch for 0.103.0ymX versions and I and Tim will =
work together
to have something for 0.103.1 :)

> In the future there will be development and live versions.  Right now I

This is not future but present :)
Development versions are here :
http://pagesperso.laposte.net/ymettier/perfparse-devel/

Well, you mean official development versions :)

[...]

> Before this is included in the release version, we need to think about
> making the provided facilities concurrent with the existing services.
>
> Let me list these below and we can comment on whether these are needed
> for release or can wait:
>
> 1/
>
> We need to ensure that we have the control option on the parsing, to se=
t
> whether the user gets this data or not.  On current methods, I suggest =
a:
> 	--no-raw-summary-data
> Flag.
>
> At the moment the single --no-raw-data flag will block both raw and raw
> summary. :)

This will be a important point. When --no-raw-data is enabled (that means=
 the feature is
disabled - I hate negative options) the storage_module is not even called=
. So the
discussion will be :
do we ask the module to test --no-raw-data, or do we add a callback for s=
ummary ?

In the discussion, we will also have to think how to have raw data in one=
 module and no
raw data in another module.

This is not very simple and the impact can be large :)

> 2/
>
> The deletion policies can wait a while.  After all, the point of these
> files is for long term storage.  But this must come at some time.

I don't agree. I have a small database here. And I get a huge amount of p=
erf data.
This is not tuned (still testing nagios), but it's good to test nagios an=
d perfparse
limits :)
Well, this is my problem.
But my problem is also that I have to keep only 2 or 3 days of data.

Yves
--=20
- Homepage    - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key     - http://ymettier.free.fr/gpg.txt                    -
- Maitretarot - http://www.nongnu.org/maitretarot/                 -
- Perfparse   - http://perfparse.sf.net/                           -