1.42. Release Notes 0.965¶
1.42.1. Important changes in this release¶
If you created your nw2.conf file by copying nw2.conf.minimal, then please find the line that looks like this in it:monitor.variableSelector = "variable_selector.Selector"
and change it to look like this:
monitor.variableSelector = "variable_selector.VariableSelector" - the following file have moved to another location, please check if you have them in the "home" directory and delete them:: nw2rules.py tag_selector.py variable_selector.py view_builder.py
1.42.2. New features and improvements in this release¶
monitor writes report that lists numebrs of monitoring variable instances per device. This can be used to optimize amount of polling. You can find this report in the directory “reports/$network_name/monitor/0” in application’s home directory. This report is created every time monitor reconfigures itself, which happens after restart and after each network discovery.
This version comes with support for the Python hook script “tagSelector” that can be used to add device and interface tags. This script can also be used to parse interface descriptions and add tags using information found there. See documentation file tags.md for more information and examples
This version comes with support for discovery and monitoring of VMWare servers. NetSpyGlass can discover and monitor basic parameters of the host (host platform, software revision, network interfaces), inventory of virtual machines and virtual switches. Virtual switches appear on maps as autogenerated devices with the name composed from the name of the virtualization server and corresponding port group; virtual machines appear connected to the virtual switches. This provides insight into virtualized network topology.
Virtualization server gets role tag “VMServer” and virtual machines get role tag “VM”. These tags can be used as part of the logic that decides which variables we should monitor if you want to monitor different sets on VMs (see doc monitoring_variables.md).
SNMP agent must be activated on the host according to VMWare documentation: http://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.monitoring.doc_50%2FGUID-8EF36D7D-59B6-4C74-B1AA-4A9D18AB6250.html
NetSpyGlass assigns interface tags in facet “ifVlan”, tag word is the number of the vlan the interface is a member of. Tagged ports can get multiple tags to describe all their vlans.
Graphing Workbench displays current, minimum and maximum values for all variables, as well as color “dot” that serves as an indicator when current value is over configured thresholds. The color of the “dot” matches color of links in maps and similar “dot” in the device details pages. Note that rows in the table in the Graphing Workbench relate to different interfaces (or other hardware components) of different devices and corresponding values may span very wide range. These values are scaled and may appear displayed in different units, such as “bit/sec”, “Mbits/sec”, “Gbits/sec” and so on. Units appear in the last column of the table. The minimum and maximum values are calculated over the length of the time series that NetSpyGlass keeps in memory. See description of the configuration parameter monitor.storage.memoryPoolDurationHrs in the installation and configuration guide.
We have optimized code that loads configuration file to avoid long lived objects
1.42.3. Notable Bugs fixed in this release¶
- fixed broken “trending analysis” function in graphs.