[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rhq-devel
Subject:    Need advice about agent plugin design
From:       mazz () redhat ! com (John Mazzitelli)
Date:       2011-06-17 12:06:27
Message-ID: 4DFB4343.9060506 () redhat ! com
[Download RAW message or body]

Nice, Andreas! This sounds very interesting - looking forward to seeing 
it when you release.

Thanks,
John Mazz

On 06/17/2011 03:40 AM, Andreas Dietrich wrote:
>    Hi Steven,
>
> we will release our Logreader plugin amongst others soon. Maybe it could
> help you...
>
> Our Logreader plugin is able to capture logs or specific lines of interests.
> Its primary purpose so far is to monitor logs for errors and warnings
> and to issue an RHQ alert if they occur.
>
> We are using it successfully in various production environments now for
> quite some time for the monitoring of all kinds of different log types:
> OS logs (/var/message/log), Oracle database alert and listener logs,
> JBoss logs, RHQ logs (agent.log, rhq-server-log4j.log), specific
> application logs and many more ...
>
> You can configure it with help of Java regular expression lists, e.g.
> some simple ones ... ".* ERROR .*", ".* WARN .*", ".* ORA-\d+ .*".
> You can also exclude certain error or warning patterns in the same way,
> e.g. for known and not to be processed loglines.
> The handling for abitrary log files is quite sophisticated regarding
>
> - rolling log files
> - limits on "log/alert spam" (e.g. to report only 5 loglines per 1 min
> log check where the 4th contains a line like "... skipped 300 loglines
> due to a max loglines per check of 5")
> - optimizations for very large logfiles (e.g. start at last known
> position if file has not rolled yet, regexp handling, ...)
> - auto discovery of certain locations, types and patterns
> - capturing of historical/old loglines if needed
> - agent restarts or downtimes
>
> It stores it as traits in the database, but currently not with a
> granularity and precision as Syslog daemons do (only discovery time of
> logline, up to 4000 characters per line). (You also see the trait data
> in the GUI with up to 256 characters per line in a chronological order)
>
> More details will be available on our homepage within the next weeks.
> But if you don't want to wait we can give you the plugin to try it out
> yourself earlier.
>
> Kind regards
> Andreas :-)

[prev in list] [next in list] [prev in thread] [next in thread]