Hi,
Some of my IP cams will occasionally crap out on me with a 'Signal: Lost' log file entry. What's the nomenclature for this in filter speak? So far, I've tried [Notes|Cause] + [equal to|matches] + 'Signal: Lost', but to no avail. This is Zoneminder v. 1.25.0 on a Debian 7.6 box with working e-mail notification via SMTP on localhost.
Any pointers greatly appreciated!
Thanks, Mike
Filtering: Syntax for Signal Lost Event?
Re: Filtering: Syntax for Signal Lost Event?
I fear you may be looking in the wrong place -- I'd be happy for someone to shoot this down though 
If you are using the "filters" tab, that is for filtering Events -- that's where I see "Notes" and "Cause" fields.
You're not looking for events, but for log entries -- I don't think an event is created for "Signal Loss"
The filtering under the "Logs" tab (top right on 1.25) isn't as flexible as that for events, but at least it's the right place to be looking.
Failing that,
may get you somewhere by hand
If you are using the "filters" tab, that is for filtering Events -- that's where I see "Notes" and "Cause" fields.
You're not looking for events, but for log entries -- I don't think an event is created for "Signal Loss"
The filtering under the "Logs" tab (top right on 1.25) isn't as flexible as that for events, but at least it's the right place to be looking.
Failing that,
Code: Select all
grep "Signal: Lost" /var/log/zm/zm.logRe: Filtering: Syntax for Signal Lost Event?
Hey,
I think you might be on to something here Before I go a bash-ing my log entries, can someone please confirm?
Bests, Mike
I think you might be on to something here
Before I go a bash-ing my log entries, can someone please confirm?Bests, Mike
Re: Filtering: Syntax for Signal Lost Event?
Well, to add insult to injury, a 'Signal: Reacquired' will actually trigger a filterable event (via 'cause' => 'Signal'). Same daemon (zm_monitor) AFAIK, so where do I need to start digging?
Re: Filtering: Syntax for Signal Lost Event?
What exactly are you trying to do? Your original post wasn't clear about what your goal was.
Are you trying to prevent an event from being logged if you have a Signal Loss?
https://github.com/ZoneMinder/ZoneMinde ... .cpp#L1410
https://github.com/ZoneMinder/ZoneMinde ... .cpp#L1469
are the places where an Event is created. If you go through that file, you will find various parts of the code that sets signal and last_signal to start/stop signal recording conditions. If you want to dig around, I suspect reading that file carefully and masking out the event creation (and event stop) for a signal change is probably what you will need to do and re-compile. I don't think there is any way to do it without changing code.Obviously, change comes at its own peril - please make sure you take care of doing a clean job of it by assessing if any other condition will be affected.
If instead you are looking at a way to delete all events of type 'signal' after they are created in a scheduled fashion, filters is probably the way to go ==> filter by cause field - it will be Signal for the events you want to process/delete
Are you trying to prevent an event from being logged if you have a Signal Loss?
https://github.com/ZoneMinder/ZoneMinde ... .cpp#L1410
https://github.com/ZoneMinder/ZoneMinde ... .cpp#L1469
are the places where an Event is created. If you go through that file, you will find various parts of the code that sets signal and last_signal to start/stop signal recording conditions. If you want to dig around, I suspect reading that file carefully and masking out the event creation (and event stop) for a signal change is probably what you will need to do and re-compile. I don't think there is any way to do it without changing code.Obviously, change comes at its own peril - please make sure you take care of doing a clean job of it by assessing if any other condition will be affected.
If instead you are looking at a way to delete all events of type 'signal' after they are created in a scheduled fashion, filters is probably the way to go ==> filter by cause field - it will be Signal for the events you want to process/delete
canut wrote:Well, to add insult to injury, a 'Signal: Reacquired' will actually trigger a filterable event (via 'cause' => 'Signal'). Same daemon (zm_monitor) AFAIK, so where do I need to start digging?
I no longer work on zmNinja, zmeventnotification, pyzm or mlapi. I may respond on occasion based on my available time/interest.
Please read before posting:
How to set up logging properly
How to troubleshoot and report - ES
How to troubleshoot and report - zmNinja
ES docs
zmNinja docs
Please read before posting:
How to set up logging properly
How to troubleshoot and report - ES
How to troubleshoot and report - zmNinja
ES docs
zmNinja docs
Re: Filtering: Syntax for Signal Lost Event?
My apologies for being a bit unclear in my initial posting. I would like to get notified by e-mail about a signal loss for any of those cameras. This appears to be working for 'Signal: Reacquired' events but not for 'Signal: Lost'. Kudos, BTW, for your great work explaining ZM's zoning system! This cleared up for me a couple of concepts that have been puzzling me for a while.
Bests, Mike
Bests, Mike