Details

      Description

      currently there is no easy way to determine what a user macro will resolve to. this requires checking three locations if looking at a host linked to a single template (global, template, host), but if nested templates are used, this becomes a hard task.

      a macro resolution feature would help. probably available on a host/template level, it would show value macro would have and where the value originates.
      ideally it would also warn if macro resolving is ambiguous - for example, same macro is defined in multiple same level templates that are linked to a single host.

      Specification

        Attachments

        1. macro_resolving_2.png
          macro_resolving_2.png
          4 kB
        2. macro_resolving.png
          macro_resolving.png
          4 kB
        3. ZBXNEXT-210_2.2.1-example.png
          ZBXNEXT-210_2.2.1-example.png
          35 kB
        4. ZBXNEXT-210_show_all_macro_values-2.2.1.patch
          9 kB
        5. ZBXNEXT-210_show_all_macro_values-2.4.2.patch
          11 kB
        6. ZBXNEXT-210-2.0.9.png
          ZBXNEXT-210-2.0.9.png
          27 kB
        7. ZBXNEXT-210-2.0.9-1.patch
          7 kB
        8. ZBXNEXT-210-2.0.9-1.png
          ZBXNEXT-210-2.0.9-1.png
          28 kB
        9. ZBXNEXT-210-2.0.9-2.png
          ZBXNEXT-210-2.0.9-2.png
          26 kB
        10. ZBXNEXT-210-2.0.9-4.patch
          10 kB
        11. ZBXNEXT-210-2.0.9-4.png
          ZBXNEXT-210-2.0.9-4.png
          45 kB
        12. ZBXNEXT-210-2.0.9-5.patch
          10 kB
        13. zbxNext210-2.2.5.patch
          10 kB
        14. zbxNext210-2.2.5-2.patch
          10 kB

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                richlv richlv
              • Votes:
                18 Vote for this issue
                Watchers:
                15 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: