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

allow structured transfer of entities from the frontend

XMLWordPrintable

    • Icon: New Feature Request New Feature Request
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • 3.0.3
    • Frontend (F)
    • None

      (an old idea, but i can't find an existing issue. sorry if this is a dupe)

      when one wants to recreate item, trigger or any other entity from one zabbix instance in another, it requires careful manual work.
      xml import/export can be used when whole hosts/templates/screens/maps have to be transferred, and item/trigger copying can be done on the same zabbix instance, but they both are quite limited.

      it would be nice to copy structured data from an entity configuration form (item, trigger, global regexp, value map...), then paste it in another entity config form and get all the fields populated. it would also be a bit more flexible than item/trigger copying - one could modify the copied text before pasting.

      the data might make sense to expose as json, maybe even matching the api output, where applicable.

      concerns :

      • validation - the inserted text should be fully verified and forms should not be filled partially - if there's anything not right, the whole input should be rejected
      • version compatibility - it might make sense to design the contents with versions in mind right away. maybe even including zabbix version in there

      this could be useful for nearly all entities :

      • items
      • triggers
      • users
      • maps
      • screens
      • global regexps
      • value maps
      • web scenarios
      • network discovery rules
      • actions
      • media types
      • user media
        ...

            Unassigned Unassigned
            richlv richlv
            Votes:
            4 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: