You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Trap Visualizer receives data key and values that get lost in the switch case. Will need to match all possible values so the data is collected, sorted and drawn correctly in the graph.
I also want to include more options for the Visualizer Graph including a dual or triple layer D3 graph and the ability to view any graph type against any trap data column. Lastly, I'd like to include an option for the graphs to be against a specific column such as hostname, OID, eventname, formatline, etc.
This will tie into, and improve, the ability to generate nice graph supported reports inside Nagios XI thorugh the NSTI plugin for Nagios XI. The plugin will include wkhtmltopdf and include the users choice of graph(s) and tables with or without filters using the API.
Not exactly sure I know what's going on at this point - simply want to acknowledge the bug. I'm going to leave this milestone open and add a needs review label so I get back to it.
The Trap Visualizer receives data key and values that get lost in the switch case. Will need to match all possible values so the data is collected, sorted and drawn correctly in the graph.
I also want to include more options for the Visualizer Graph including a dual or triple layer D3 graph and the ability to view any graph type against any trap data column. Lastly, I'd like to include an option for the graphs to be against a specific column such as hostname, OID, eventname, formatline, etc.
This will tie into, and improve, the ability to generate nice graph supported reports inside Nagios XI thorugh the NSTI plugin for Nagios XI. The plugin will include wkhtmltopdf and include the users choice of graph(s) and tables with or without filters using the API.
Bug from this Nagios Support Forum topic:
http://support.nagios.com/forum/viewtopic.php?f=22&t=27521
The text was updated successfully, but these errors were encountered: