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

Add macros support for update intervals

XMLWordPrintable

    • Sprint 1, Sprint 2, Sprint 3, Sprint 4, Sprint 5, Sprint 6, Sprint 7, Sprint 8, Sprint 11
    • 28

      Hi, having the possibility to define update intervals with macros would be a nice addition.

      Example:

      {$FAST} = 60 sec
      {$NORMAL} = 120 sec
      {$SLOW} = 300 sec
      {$VSLOW} = 3600 sec

      With this interval I can cover 99% of my items and changing one of them would update all the hosts within a template. Furthermore I could easily relax checks for specific hosts with slow connectivity or behind proxies.

        1. working_time_error.png
          working_time_error.png
          32 kB
        2. undefined_index_graphs.png
          undefined_index_graphs.png
          99 kB
        3. screen.png
          screen.png
          115 kB
        4. same_update_intervals.png
          same_update_intervals.png
          37 kB
        5. problem_view_query_failed.png
          problem_view_query_failed.png
          89 kB
        6. min-mon.png
          min-mon.png
          4 kB
        7. latest_data.png
          latest_data.png
          84 kB
        8. failed_status_of_zabbix.png
          failed_status_of_zabbix.png
          89 kB
        9. error-message.png
          error-message.png
          33 kB
        10. discovered_item_editing.png
          discovered_item_editing.png
          34 kB
        1.
        		 Documentation for Add macros support for update intervals Change Request (Sub-task) Closed Unassigned
        2.
        		 Proper implementation of DBmodify_field_type() for Oracle database Change Request (Sub-task) Closed Unassigned

            gcalenko Gregory Chalenko
            c.mammoli Cristian Mammoli
            Team A
            Votes:
            33 Vote for this issue
            Watchers:
            31 Start watching this issue

              Created:
              Updated:
              Resolved: