[ZBXNEXT-2251] Describe logseverity levels in a documentation. Created: 2014 Apr 10  Updated: 2014 Oct 23  Resolved: 2014 Jun 20

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Documentation (D)
Affects Version/s: None
Fix Version/s: 2.2.0

Type: Change Request Priority: Trivial
Reporter: Oleg Ivanivskyi Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: eventlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate

 Description   

Please improve the documentation (https://www.zabbix.com/documentation/2.2/manual/appendix/triggers/functions) and add a description of possible values for "logseverity" trigger function:

1 Informational
2 Warning
4 Error
7 Failure Audit
8 Success Audit
9 Critical
10 Verbose



 Comments   
Comment by Constantin Oshmyan [ 2014 May 27 ]

This issue was added by Oleg upon my request.
I'd like to clarify my point of view.
The documentation claims that the "logseverity" trigger function returns an "integer, useful for Windows event logs". However, when we are constructing the trigger expression, we need to know the exact values for comparison. Unfortunately, these values still undocumented. For me, for example, it was necessary to search using google; I found an examples on Zabbix forum only. Finally, the real full list of these values I found in the sources (file include/common.h, group of constants ITEM_LOGTYPE_*). It is absolutely unnecessary troubles and lost of my time: evidiently, these constants must be documented.

Sincerely yours,
Constantin Oshmyan

P.S. NB! Real values returned by the "logseverity" trigger function look to be just as in this include file. It differs from the examples provided by Oleg!

Comment by Oleg Ivanivskyi [ 2014 May 31 ]

Thanks Constantin, "logseverity" levels updated.

Comment by Martins Valkovskis [ 2014 Jun 20 ]

Documentation improved in https://www.zabbix.com/documentation/2.2/manual/appendix/triggers/functions

Thanks for reporting.

sasha Thanks! CLOSED

Generated at Thu Apr 25 18:40:46 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.