Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 17:04:34 2016
|
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 |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 17:21:56 2016
|
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 |
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 18:37:32 2016
|
Where is this feature documented?
Stefan
Ritt wrote:
You guys know that there is the possibility to execute an arbitrary |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 19:08:09 2016
|
In the documentation of course :-)
Tamas
Gal wrote:
Where is this feature documented? |
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 19:13:47 2016
|
I'm probably too tired or I don't know, but of course I looked at the user's guide and the admin's guide but did not found anything about
this ;-) Is there another documention which I missed somehow?
Stefan |
|
Re: Monitoring a logbook for changes, posted by Stefan Ritt on Wed Jan 13 19:22:35 2016
|
You look here: http://midas.psi.ch/elog/config.html and scroll down to "Execute New". I wonder how you ever could run elog without looking
at that page.
Tamas |
|
Re: Monitoring a logbook for changes, posted by Tamas Gal on Wed Jan 13 19:26:35 2016
|
OK thanks I'll check that out. I did not configure ELOG by myself, I only use it and wrote the Slack plugin ;-)
Stefan
Ritt wrote:
You look here: http://midas.psi.ch/elog/config.html and scroll |
|
Re: Monitoring a logbook for changes, posted by Johan Forsberg on Wed Jan 13 20:08:04 2016
|
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 |