1.2. Release Notes 2.1.2¶
this is a bug-fix release
1.2.1. Improvements and new features¶
- Integration with Kentik: NetSpyGlass uses filter that matches interfaces by name and includes both parent interface and all its subinterfaces. This way, NetSpyGlass can get information from Kentik regardless of the type of the interface that appears in maps (physical port, e.g. “ae0” or subinterface, such as “ae0.0”). This filter works automatically for both switch ports and router interfaces.
- NET-1929: NsgQL: add column “snmpName” to the table “interfaces”. The value of this column is this interface’s full name obtained by querying OID “ifDescr”. This name can be used with Kentik query filters
- Numberous optimizations in NsgQL make typical NsgQL queries faster
- TSDB connector for Graphite: configuration parameter uploadSpreadTime can be changed without server restart; The server does not create a copy of the monitoring data to be sent to Graphite, this helps avoid problems with memory footprint that happened when Graphite had an outage or was temporarily down
- server should refuse to load devices from the configuration in case of errors and displays both brief and detailed information about generated errors and warnings in the UI as well as in the log.
1.2.2. Bugs fixed in this version¶
- NET-1928 interface popup in a map: list of tag facets shows duplicate items
- (no number): fixed bug that prevented NetSpyGlass processes from properly recovering after disconnect and subsequent reconnect to Zookeeper ensemble
- NsgQL query
SELECT time,metric FROM variable ORDER BY metricsorts variables by the value of the last observation in the time series and returns observations in the correct chronological order. It should not sort data points according to their values which breaks chronological order. The sorting behaves just as if the query was
`SELECT time,tslast(metric) as last FROM variable ORDER by last
- NsgQL operator “NOT IN” should return true when the row has no data in the column