This is a brief overview of the major changes between opCharts releases.
...
- The Metrics and Health component has been extended to group by any node configuration property.
- This is set in opCommon.nmis opcharts_metric_summarise_by, you need to define an array of hashes, with key and name
{
'key' => 'group',
'name' => 'Group'
},- If more than one selector is defined on the top left of the Metrics and Health component a dropdown is shown to change which confiuration item the nodes are grouped by.
- Metrics and Health gauges are now rendered in one row which are scroll-able to the right.
- Metrics and Health links now correctly affect the nodes filter when clicked.
- Metrics and Health is now searchable on the currently selected column.
- New Event History component which utilizes the NMIS9 events DB
- For this to work in opCharts you need to set keep_event_history => 'true' in NMIS9 Config.nmis
- Consideration should be given to the volume of data on the pollers and master and how much event history will be kept, by default NMIS9 will keep 7 days of event history which is configured in Config.nmis/purge_event_after (7*86400), if having problems viewing event history, reduce the number of days and purge the data.
- This component replaces the old tail log event viewer but if you want to use the old component change opcharts_db_event_history to 0 in opCommon.nmis
- Currently websockets are not enabled, this component is set to refresh period
- Revised Events screen to utilize the new Event History component
- Fixed issue where adding a group to a map would cause the node selection modal to appear
- Fixed issue where the nodes interfaces panel which shows interfaces with oper status down would fail to render
- Fixed issue where the nodes interface component would incorrectly show certain interfaces
- Fixed issue where the node selector on the nodes screen will fail to render if a group name is numeric
- Fixed issue where the TopN table text would not correctly space the table contents
- Fixed issue where a node info panel would cause a 500 if the node does not exist
...
Released August 22th, 2019
opCharts 4.0.7 requires NMIS 9.0.6
- Fix TopN query error in master servers with lots of data from the poller servers. The error was a MongoDB::DatabaseError: operation exceeded time limit.
- New Admin function to set many user's default dashboard:
./opcharts-cli.pl act=import-user-dashboard name=dashboard-name users='user1, user2, ...'
- Fixed changing the default dashboard for a user in the GUI.
- NMIS button works for non local servers now: Redirects to the NMIS node poller view.
- GUI improvements:
- Fixed size in NMIS button (Nodes View) and set visible as default.
- Improve view for long group names in Metrics and Health view, not overflowing.
- Improve the view for long names in TopN table.
- Support for watching monitored services graphs from the poller servers in the master.
- Fixed bug that prevented hiding ssh button in node info panel where it was disabled using opcharts_gui_display_node_ssh.
- Fixed bug that was failing to check permissions for a subnet.
opCharts 4.0.6 Beta
Released July 19th, 2019
opCharts 4.0.6 requires NMIS 9.0.4
...
opCharts 3.3.6
To Be Released November 2729th, 2019
opCharts 3.3.6 requires NMIS 8.6.2G
...
- Refreshed login screen for all OMK applications
- Improved node searching speed, set nmisx_db_cache_enable => 1 in opCommon to take advantage of this.
- Chart editor now supports negative number in the multiply field
- Stacked charts can now display min/max/avg values for the sum of the stack
- Caching of subnets has been improved to decrease the risk of the file being locked when it needs to be read.
- Updated systemd compalbity for opmantek services, see more here.
- Updated the logrotate script for systemd
Bug Fixes
- Fixed issue with update-subnet-dependancy
- opCore Node editor was setting the wrong key for collect_snmp
- Node editor logs the current user in the audit.log when node config is changed
- Fixed issue where the failure flash message was not displayed
- Fixed issue where monitored service graphs had no date-time value
...