[ZBXNEXT-470] Expand (return) support of the Severity levels displayed in history for eventlog (needs for custom syslog solution). Created: 2010 Aug 07 Updated: 2015 Aug 25 |
|
Status: | Open |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Frontend (F) |
Affects Version/s: | 1.8.2 |
Fix Version/s: | None |
Type: | New Feature Request | Priority: | Major |
Reporter: | Oleksii Zagorskyi | Assignee: | Unassigned |
Resolution: | Unresolved | Votes: | 4 |
Labels: | severity, syslog | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
last trunk |
Attachments: |
![]() ![]() ![]() ![]() ![]() |
Description |
Please return and expand support of the Severity levels displayed in the history. In version 1.8.1 the history of items supported the following severity levels to display (i.e. there were 5 different severity levels): After I ask to return severities 3 and 5, plus add a severity for 6. Why I'm asking:
The result can be seen on next two pictures: This request would be convenient to perform with Just information: I plan to combine 6 and 7 as well as 0 and 1. That will be enough. |
Comments |
Comment by Oleksii Zagorskyi [ 2010 Aug 07 ] |
I am a little confused and mistaken - support for "3 - Warning" is not necessary. Now it is in the severity of "2". If you agree, perhaps more easily and correctly, will realize the severity for example in the new range of 10-17 but 100% accurate according to the RFC3164. |
Comment by Oleksii Zagorskyi [ 2010 Sep 15 ] |
My last suggestion (new range 10-17) coincides with this excellent solution - zbxlog. Attaching sources archive here (v 1.5), just in case. |
Comment by Oleksii Zagorskyi [ 2012 Aug 31 ] |
Just a note - currently in 2.0.2 the page "history.php" shows all columns (as for windows eventlog) only for items with a key "eventlog[...]" Just in case see |
Comment by Oleksii Zagorskyi [ 2013 Jun 23 ] |
ZBXNEXT-1798 asks more severities for triggers |
Comment by Oleksii Zagorskyi [ 2015 Aug 25 ] |
Just to keep things linked - there is another (a bit similar to zbxlog, though) solution for syslog monitoring. |