XMLWordPrintable

    • Prev.Sprint, S25-W10/11, S25-W12/13, S25-W14/15, S25-W16/17, S25-W18/19, S25-W20/21, S25-W22/23, S25-W26/27, S25-W30/31, S25-W34/35, S25-W38/39, S25-W42/43
    • 15

      in some cases one-level lld is not enough. for example, one might want to discover all databases and then discover all tables for them, to monitor some statistic for all of them.

      this might be doable by creating some sort of "lld rule prototype", which could then cascade almost indefinitely (although i can't think of more than 2 level practical application right now)

        1. lld_res_removal_host.yaml
          1 kB
          Dmitrijs Goloscapovs
        2. zbx_export_templates.json
          15 kB
          Vladislavs Sokurenko
        3. template_with_3_levels_of_nested_LLDs.yaml
          7 kB
          Sergejs Olonkins
        4. server_log_for_nested_lld_issue.log
          1.64 MB
          Sergejs Olonkins
        5. screenshot-1.png
          14 kB
          Sergejs Olonkins
        6. screenshot-2.png
          15 kB
          Sergejs Olonkins
        7. host_for_testing_nested_lld.yaml
          5 kB
          Sergejs Olonkins
        8. proxy_log_for_not_working_nested_lld_discovery.log
          542 kB
          Sergejs Olonkins
        9. host_with_3_levels_of_nested_LLDs (2).yaml
          4 kB
          Deniss Ponomarenko
        10. template_with_nested_lld_host_prototypes.yaml
          4 kB
          Sergejs Olonkins
        11. zabbix_server_failed_to_unlink.log
          358 kB
          Sergejs Olonkins
        12. zabbix_server_failed_to_unlink-1.log
          358 kB
          Sergejs Olonkins
        13. template_for_deletion_via_autoreg.yaml
          8 kB
          Sergejs Olonkins
        14. 58.yaml
          2 kB
          Dmitrijs Goloscapovs

            Assignee:
            Andris Zeila
            Reporter:
            richlv
            Team D
            Votes:
            145 Vote for this issue
            Watchers:
            99 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0h
                0h
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 521.5h
                521.5h