Re: [Perfparse-users] monitor perfparsed with nagios

[Yves <yme...@pe...>]

>> When perfparsed breaks, if you can find the reason, tell us, and we'll=
 try to find a
>> way
>> to make perfparsed do something else than break.
>
> well, whenever there is a problem with one of the storage modules, it
> simply exits:
> e.g. if the db is unavailable or (like I had this morning) the
> filesystem where the db resides is full. Last week I tried to use the
> file_output and mysql storage modules, but the file_output module
> would not load (haven't figured out why yet, it just said
> "storage_file_output module failed to initialize itself").  In all
> these cases, perfparsed exited.

OK. In those cases, I consider that perfparsed should exit. I was just th=
inking about
cases where perfparsed could deal with the situation and does not. If the=
re are any :)

> The question of course is, what should perfparsed do? Should it exit
> or not? I don't think there's a simple answer to that, except that in
> case of failure, I'd like to know about it :) One place I look at is
> the error log. The things I'd like to add to the error log is some
> extra info when a module is succesfully initialised, a bigger buffer

storage_%s module successfully loaded\n", storage_name
done :)

> for error messages (they get truncated at 256 chars), and a clear

#define LOG_MESSAGE_LENGTH 1024

Is that OK for you ?

> 'perfparsed stopped' message whenever there is a fatal error.

Done (thanks to already implemented atexit function :)

This is available in few minutes in perfparse-0.104.2ym2 on
http://pagesperso.laposte.net/ymettier/perfparse-devel/

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/                           -