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

GUI uses only *Local* node configuration disregarding on selected node to view.

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Won't fix
    • Icon: Blocker Blocker
    • None
    • 1.8.10
    • Frontend (F)

      See the SQL queries from the GUI debug section.
      There the "nodetype=1" is the Local node for the GUI and its configuration is used in the time when I've selected Current node "NodeID=2" (child) in the top right corner.

      Time:8.2E-5 SQL: SELECT * FROM nodes WHERE nodetype=1 ORDER BY nodeid
      ................
      Time:9.0E-5 SQL: SELECT * FROM config WHERE ((configid BETWEEN 100000000000000 AND 199999999999999))
      .................

      I understand that the authorization and the checking of user rights is performed based on Local node and it's ok, but nodes configuration can be different and it should be used for particular selected node in the GUI.

      When this problem considered as critical:
      some node uses acknowledges and some not. in this case an inheriting GUI displaying the Local node configuration is not very good;
      some node is "big" and a mode "Dropdown first entry -> None" is only possible to use, another node is "small" and "Dropdown first entry -> All" is much better than "None". For instance usually for master node the mode "None" is optimal but when selecting a child node seems "All" will be more useful.

      Configuration from Local node could be used only if in the Current node we have selected "All" (nodes)

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

              Created:
              Updated:
              Resolved: