[ZBXNEXT-3132] Why reinvent the wheel by providing in-house web based map creation tool? If there would be well supported import/export format, one could create and modify maps in external tool which is specialized for such purpose. Created: 2016 Feb 04  Updated: 2017 Feb 01

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F)
Affects Version/s: 2.2.11, 2.4.7
Fix Version/s: None

Type: New Feature Request Priority: Trivial
Reporter: Mārcis Lielturks Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: export, import, maps
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Just brainstorming here in hope that somebody would pick this up and either drop as not feasible idea or iron out further details (been "sitting" on this for a while, hoping I'll have more time to iron out the proposal, but that doesn't seem to happen).

There are several graph file formats. Many of the formats allow nodes and edges to have custom meta data (properties). As manual map creation in front-end tends to be tedious task, maybe front-end should offload this functionality to external applications and only provide support for some standard graph import/export format. This would require to define additional constraints (on top of original graph format) on graph elements (so Zabbix can map graph elements to Zabbix objects (hosts, triggers, other maps, icons etc.).

I personally use yEd [1] for drawing graphs and it uses GraphML format (XML), but that's just an example, there are other formats and application too (I used Dia [2] in the past). Hey, maybe there are even use case for Zabbix supporting Visio's format (I think VSDX was "open").

[1] https://www.yworks.com/products
[2] https://wiki.gnome.org/Apps/Dia



 Comments   
Comment by Volker Fröhlich [ 2016 Feb 04 ]

It's easy enough to transform the export format yourself.

Comment by Aleksandrs Saveljevs [ 2016 Feb 08 ]

Related ZBX-4855 and ZBXNEXT-272 (XML documentation and schema) might help here.

Generated at Wed Apr 24 06:25:14 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.