[ZBXNEXT-448] New trigger function support - logeventid Created: 2010 Jul 08 Updated: 2011 Mar 23 Resolved: 2011 Mar 18 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 1.8.2 |
Fix Version/s: | 1.8.5, 1.9.3 (alpha) |
Type: | New Feature Request | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Rudolfs Kreicbergs |
Resolution: | Fixed | Votes: | 9 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Description |
It must check if EventID of the last log entry matches parameter. =1 Use this feature very useful for Templates if there are servers or workstations with different Locales, as the text of messages in them are different but number of EvenID is identical. I think this feature was not just because the support of EventID generally appeared recently in v1.8. Something of this in the first post: http://www.zabbix.com/forum/showthread.php?t=14944 |
Comments |
Comment by Oleksii Zagorskyi [ 2010 Jul 09 ] |
additional forum post http://www.zabbix.com/forum/showthread.php?t=17102 |
Comment by Oleksii Zagorskyi [ 2010 Sep 18 ] |
I've been wanting to write, and that's just the case turned up Although I specifically stated in the beginning of that "in ARGUMENT need to accept single number of EventID", but lately am sure that it would be better to incoming ARGUMENT supports regular expressions. There is a lot of sense if you've worked for finding problems with the windows servers you will understand why. This will write the expressions triggers much shorter than if a single ARGUMENT. =1 And anyway, I think that the function 'logseverity' not entirely logical, is inconvenient, as the way you can see a lot of user error on the forum. I would put a goal to make it look like on my last sentence, namely that the incoming ARGUMENT supports regular expressions and returns the output 1 or 0. Then it be standardized with other trigger functions. =1 =1 I understand that this is the subject for another ZBXNEXT, if necessary, I'll create it. |
Comment by richlv [ 2010 Dec 19 ] |
i'd agree that it would make sense to support regexps right away in such a function |
Comment by Oleksii Zagorskyi [ 2010 Dec 20 ] |
Richlv, you wrote this comment when I have a great national feast day of St. Nicholas. |
Comment by Oleksii Zagorskyi [ 2011 Mar 14 ] |
before the work will be done can you say me how is your decision? this trigger function will be support a regexp or not? |
Comment by Rudolfs Kreicbergs [ 2011 Mar 15 ] |
logseverity should be addressed in a seperate ZBXNEXT since the current functionality ignores the argument and returns the severity, thus it should be discussed some more. |
Comment by Rudolfs Kreicbergs [ 2011 Mar 15 ] |
Available in dev branch: svn://svn.zabbix.com/branches/dev/ZBXNEXT-448 |
Comment by Aleksandrs Saveljevs [ 2011 Mar 15 ] |
(1) It should be documented that both dayofmonth() and logeventid() are available since 1.8.5. |
Comment by Aleksandrs Saveljevs [ 2011 Mar 15 ] |
(2) Please review my changes in r18446. If you like them, feel free to merge. |
Comment by Rudolfs Kreicbergs [ 2011 Mar 17 ] |
Available in pre1.8.5 r18491 and pre1.9.3 r18494. |
Comment by Oleksii Zagorskyi [ 2011 Mar 17 ] |
Global regexps doesn't supported in the logeventid function at the server side. =1 Server debuglog: Global regexp exist: Event come with ID 70 or 50. Regular trigger like a {it2:eventlog[Test].logeventid(^70$|50)}=1 works well. |
Comment by Rudolfs Kreicbergs [ 2011 Mar 18 ] |
Added global regex support. Available in dev branch: svn://svn.zabbix.com/branches/dev/ZBXNEXT-448 |
Comment by Oleksii Zagorskyi [ 2011 Mar 18 ] |
Dev branche tested (r18531). Server side debuglog: ] len 44 ] |
Comment by Rudolfs Kreicbergs [ 2011 Mar 18 ] |
The devbranch svn://svn.zabbix.com/branches/dev/ZBXNEXT-448 is based on 1.8 branch. The issue noticed is likely to be caused by using this branch with a DB for the pre1.9.3 branch. |
Comment by Oleksii Zagorskyi [ 2011 Mar 21 ] |
Thanks Rudolfs, you are right. Global regexp works !!! Why did I go wrong: |
Comment by Rudolfs Kreicbergs [ 2011 Mar 23 ] |
Fixed/available in pre-1.8.5 r18624 and pre-1.9.3 r18629 |