Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-11508

Handling of boolean type not correct

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Minor Minor
    • None
    • 3.0.4
    • Proxy (P), Server (S)
    • None

      The manual states that using a data type of boolean should have the following behaviour:

      "Data type is used for integer items in order to specify the expected data type:
      Boolean - textual representation translated into either 0 or 1. Thus, 'TRUE' is stored as 1 and 'FALSE' is stored as 0. All values are matched in a case-insensitive way. Currently recognized values are, for:
      TRUE - true, t, yes, y, on, up, running, enabled, available
      FALSE - false, f, no, n, off, down, unused, disabled, unavailable
      Additionally, any non-zero numeric value is considered to be TRUE and zero is considered to be FALSE."

      As stated, any non-zero numeric values should be considered a boolean True and thus should be translated as "1" in the history. This is currently not the case in Zabbix 3.0.4. A value of '2' is stored without translation.

        1. screenshot-1.png
          50 kB
          Raymond Kuiper
        2. screenshot-2.png
          18 kB
          Raymond Kuiper
        3. screenshot-3.png
          29 kB
          Raymond Kuiper

            zabbix.dev Zabbix Development Team
            qix Raymond Kuiper
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: