Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-470

Expand (return) support of the Severity levels displayed in history for eventlog (needs for custom syslog solution).

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 1.8.2
    • Frontend (F)
    • last trunk

      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 ZBX-2077 (added support of Failure / Success Audit eventlog severity) severity levels of events became exactly as in Windows. At the same time in revision 10518 interpretation of events has been lost with for severity levels 3 and 5:

      I ask to return severities 3 and 5, plus add a severity for 6.
      Naming them as:
      3 - Warning
      5 - Critical (perfectly suited for ZBXNEXT-427)
      6 - Emergency
      All these levels currently are free, and for the future they will be quite universal names.

      Why I'm asking:
      I use and want to publish a solution I made (a script that is very beautiful and interesting treats Syslog) (both from servers and from different hardware).
      Using items with Type of information "Text" is ideal for this situation.

      Later a "zbxlog" solution has been published, which is much more complete than mine, see comments below.

      The result can be seen on next two pictures:

      This request would be convenient to perform with ZBXNEXT-427

      Just information:
      According to RFC3164 supports the following severity levels:
      0 Emergency: system is unusable
      1 Alert: action must be taken immediately
      2 Critical: critical conditions
      3 Error: error conditions
      4 Warning: warning conditions
      5 Notice: normal but significant condition
      6 Informational: informational messages
      7 Debug: debug-level messages

      I plan to combine 6 and 7 as well as 0 and 1. That will be enough.

            Unassigned Unassigned
            zalex_ua Oleksii Zagorskyi
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: