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

Support for trigger expressions with more than 255 characters

    XMLWordPrintable

    Details

    • Type: Change Request
    • Status: Closed
    • Priority: Minor
    • Resolution: Duplicate
    • Affects Version/s: 2.0.0
    • Fix Version/s: None
    • Component/s: Frontend (F)
    • Labels:
    • Environment:
      # zabbix_server -V
      Zabbix server v2.0.0rc3 (revision 26482) (22 March 2012)
      # mysqld -V
      mysqld Ver 5.1.41-3ubuntu12.10 for debian-linux-gnu on x86_64 ((Ubuntu))

      Description

      Related to: https://support.zabbix.com/browse/ZBX-4302

      Currently it is not possible to add a trigger with an expression which has more than 255 characters.

      In my case, my trigger expression is fine within the template (trigger is defined in a Template), it is less 255 characters long.
      But assigning that Template to a Host fails, as the Hostname is longer than the Template Name. Therefore the Trigger expression will be longer than 255 characters.

      The Frontend error looks like:
      ERROR: Cannot update host
      Value "'{hostname.subdomain.example.com:Item_Name.2.3.12.1.2.["

      {#SNMPINDEX}"].strlen(0)}<0|{hostname.subdomain.example.com:Item_Name.2.3.12.1.4.["{#SNMPINDEX}

      "].change(0)}=1&({hostname.subdomain.example.com:Item_Name.2.3.12.1.4.["

      {#SNMPINDEX}"].str("Active")}=1|{hostname.subdomain.example.com:Item_Name.2.3.12.1.4.["{#SNMPINDEX}

      "].str("Disconnected")}=1)'" is too long for field "expression" - 275 characters. Allowed length is 255 characters.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              skr Simon Kowallik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: