Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon3.gif   Monitoring a logbook for changes, posted by Johan Forsberg on Tue Jan 12 15:06:42 2016 
    icon2.gif   Re: Monitoring a logbook for changes, posted by Stefan Ritt on Tue Jan 12 16:10:34 2016 
    icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 08:37:42 2016 
       icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:29:54 2016 
          icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 17:04:34 2016 
             icon2.gif   Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 17:21:56 2016 
                icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 18:37:32 2016 
                   icon2.gif   Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 19:08:09 2016 
                      icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 19:13:47 2016 
                         icon2.gif   Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 19:22:35 2016 
                            icon2.gif   Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 19:26:35 2016 
                icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 20:08:04 2016 
    icon2.gif   Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 10:27:21 2016 
Message ID: 68235     Entry time: Wed Jan 13 20:08:04 2016     In reply to: 68229
Icon: Reply  Author: Johan Forsberg  Author Email: johan.forsberg@maxlab.lu.se 
Category: Question  OS: Linux  ELOG Version: ELOG V3.1.0-241 
Subject: Re: Monitoring a logbook for changes 

Aha, that's interesting too! I'll have to look more carefully through the documentation... :)

Stefan Ritt wrote:

You guys know that there is the possibility to execute an arbitrary script on each submission of a new messge? Just use "Execute new = <script>". In the script you have access to all parameters of the message. That's maybe simple than to watch the file set.

Tamas Gal wrote:

I just noticed that there are multiple messages per file, so I have to adapt the parser. I'll update this thread when I'm done!

Johan Forsberg wrote:

Yeah, I suppose something like that would be both faster and more efficient than polling ELOG itself. Fortunately the ELOG disk format looks easily parsed.

Thanks for the pointer!

Tamas Gal wrote:

I recommend monitoring directly on the server. Here is an example of a very simply Python script (https://github.com/tamasgal/elog-slack) which monitors the files very efficiently and immediately pushes notifications to Slack (slack.com). Just look at the code, it's pretty straight forward and very easy to adapt it to other (web) services.

Btw. here is an ELOG entry of it https://midas.psi.ch/elogs/Forum/68224

Johan Forsberg wrote:

Hi again!

I've another need that you probably already thought of :)

I'd like to be able to efficiently monitor a logbook for changes (new or edited posts) somehow. The most reasonable way I've found so far is to periodically poll a search that looks for posts after the time of the last poll. But that might note be very efficient, especially if the polling period gets short (or number of clients grows).

Is there some other feature that could be used for this? I was thinking maybe the ETag or Last-Modified HTTP header field could be used to show changes to a logbook by just reading the headers, but it would also require HEAD request support which does not seem to be there.

Cheers,

Johan

 

 

 

 

 

ELOG V3.1.5-fe60aaf