Incorrect link prefixes near the discovered LLD rule name and discovered item prototypes

XMLWordPrintable

    • S25-W48/49, S25-W50/51
    • 1

      According to <user documentation>, the name of a discovered item should be prefixed by the name of the LLD rule that has discovered this item, and when clicking on it the list of item prototypes of this LLD rule should be opened.

      The same approach is expected when it comes to the list of discovered LLD rules and the list of discovered item prototypes, but in reality frontend behavior is different:
      1 - In the list of LLD rules, the name of the LLD rule that discovered an LLD rule is used in prefix (which is correct), but clicking on this prefix leads to opening the configuration form of this parent LLD rule, instead of opening the list of LLD rule protoypes on this parent LLD rule.
      2 - In the list of item prototypes, on a discovered LLD rule, the name of the item prototype is prefixed with the name of the LLD rule that it belongs to, and clicking on this prefix opens the item prototype configuration form, from which this item prototype was created.
      The correct behavior in this case should be:

      • Using the name of the LLD rule that has discovered this item prototype as prefix
      • When clicking on this prefix, the list of item prototypes on the LLD prototype should be opened (the one that contains the item prototype from which this item prototype was discovered).

      Steps to reproduce:

      1. Import the following host: host_with_nested_LLD_links.yaml
      2. Send the following JSON to this host:
        ./bin/zabbix_sender -z 127.0.0.1 -s test -k trap -o '\{"data":[\{"db_name":"db1","first_path":"ts_data","ts_data":[\{"db1":"table_1","table_1":"super_table for 4"}]}]}'
        
      3. Open the list of items on host "test" and check the prefix of the discovered item (this behavior is the correct one):
        1. The prefix uses the name of the LLD rule that has discovered the item ("Root level LLD")
        2. Clicking on this prefix leads to the list of item prototypes under the LLD rule that has discovered this prototype ( list of item prototypes of "Root level LLD")
      4. Open the list of LLD rules on host "test" and theck the prefix next to the discovered LLD rule "1st level LLD"
        Result 1: the prefix refers the name of the LLD rule that has discoveed this LLD rule ("Root level LLD" - correct), but the link leads to the configuration of "Root level LLD", instead of leading to the list of Discovery prototypes under "Root level LLD".
      5. Open the list of item prototypes under the discovered "1st level LLD" LLD rule
        Result 2:
        1 - the name of the discovered item prototype "1st level item prototype" is prefixed with it's parent LLD rule ("1st level LLD") but should be prefixed with the name of the LLD rule that has discovered it ("Root level LLD").
        2 - clicking on this prefix opens a dialog with configuration of the item prototype that this item prototype was discovered form, but should open the list of item prototypes on the LLD prototype "1st level LLD" that is located on the parent LLD rule "Root level LLD".
        3 - when opening the configuration of the discovered item prototype, another variation of the problem is observed - parent LLD rule ("1st level LLD") is listed in the "Discovered by" field instead of the LLD rule that has actually discovered this item prototype (which is wrong), but clicking on the value of "Discovered by" field open configuration of the original item prototype (which is correct).

      Example:

            Assignee:
            Unassigned
            Reporter:
            Sergejs Olonkins
            Team C
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - Not Specified
                Not Specified
                Logged:
                Time Spent - 29h
                29h