Answer the question
In order to leave comments, you need to log in
Zabbix 3.2 why doesn't the trigger fire?
Hello!
There is a data element that rips out lines from the log containing the substring "preprocess got existing bpa for audio file"
It looks like this: log[/opt/stc-trawl/ident/log/ident.log,"preprocess got existing bpa for audio file"]
It works, corresponding records appear in the item history:
04/04/2018 09:18:36
2018-04-04 02:18:09.236 DEBUG 29510 --- [pub-#9597%ident%] cstident.job.preprocess .Preprocess : preprocess got existing bpa for audio file = file:/data/wav/records/bb26s5pqj6jge0rnf8g0.wav
04/03/2018 17:40:34
2018-04-03 09:41:33.022 DEBUG 29510 --- [pub-#2556 %ident%] cstident.job.preprocess.Preprocess : preprocess got existing bpa for audio file = file:/data/wav/records/bb1o90hqj6jge0rnf6c0.
But there is no way to write a trigger that triggers the addition of the next line to the log.
I do this: {hostname:log[/opt/stc-trawl/ident/log/ident.log,"preprocess got existing bpa for audio file"].str(preprocess got existing bpa for audio file)}=1
but trigger does not fire when new matching lines appear in the log. What am I doing wrong?
In fact, I do not need to parse the line (if it came to zabbix, it already matches the pattern ,"preprocess got existing bpa for audio file") - I need to react to the very fact of its appearance in the log.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question