Version 18.16 - September 2019

New Features

- Viptela SD-WAN reports (16)

- Permission configuration on a role basis (270)

- Changed AWS Flow Log collection to use S3 buckets and added support for multiple regions and customer IDs (378)

- VeloCloud SD-WAN reports (550)

- Service Now Notification support (569)

- Appliance self migration from CentOS 6 to CentOS 7 (826)

- Ability to Add/remove/update Defined Applications via the API (891)

- Single-Sign-On support through SAML 2.0 (897)

- Alarm when authentication tokens will expire in 30 days or have expired (937)

- Deleting an exporter doesn’t block collection (992)

- Removed device specific status notifications (1099)

- Audit logs can now be expired after a configurable duration (1171)

- FDW option to Database migrator for faster PostgreSQL migrations (1205)

- Flow inactivity alarms are now checked across a distributed cluster and are per exporter rather than per interface (1254)

- Support for Fortinet application names (1425)

- Support Nokia (formerly ‘Alcatel-Lucent’) IPFIX (1735)

- Support for Gigamon Application Intelligence (1832)

Fixes

- Schedule emails will now use the theme from Admin > Settings > System Preferences (185)

- The ability to use an auth token with any URL (308)

- UTF8 issue with Japanese characters in email alert notifications (636)

- ‘Truncate map labels’ was grabbing an extra character sometimes (700)

- Addressed an issue with flow class sequence numbers with distributed upgrades (753)

- Removed admin restriction on running group level reports (841)

- Clarify several log error messages, and reduce their volume (846)

- Some Scrutinizer custom gadgets break the ability to add any gadget for all users (900)

- AMI: set partitions doesn’t remount pg_stat_tmp as a RAM drive (1066)

- Issue where deleted exporters may not be cleared out of LED stats table (1079)

- Issue where system updates could revert a setting causing “Panic: Can’t find temp dir” errors and the interface failing to load (1082)

- Higher default timeouts for collect asa_acl task (1085)

- Issue with special characters in PRTG integration (1117)

- Warnings when an exporter sends the same multiplier data two different ways as long as what it sends is consistent (1120)

- UNION SELECT errors in migrator (1132)

- Autofilling IP on host search from report tables (1140)

- Scheduled reports last sent time used incorrect (1142)

- SQL GROUP BY ERROR in the collector log (1145)

- Issue with Auto SNMP Update not disabling all SNMP calls (1158)

- PostgreSQL logs using too much disk space (1209)

- Special characters in notification profile breaks threshold’s ‘save & edit policy’ option (1229)

- Added stray columnar file check and alarm policy (1231)

- Monitor association of /var/db/fast and RAM spools (1239)

- Issue with running yum update on AWS EC2 instances (1249)

- Issue with load time of Admin > Host names view (1272)

- Defined application changes now realized on distributed collectors w/o a collector restarts (1297)

- Issue with alarm details and FQDN data for clusters using DB encryption (1314)

- DB disk usage stats did not always expire on distributed installs (1322)

- Collect support files includes the PostgreSQL log (1385)

- Allow snmpSystem details longer than 255 characters (1392)

- Errors from set tuning when two changes require a collector restart (1422)

- Getting Internal Server Error (500) when trying to access Maps > CrossCheck and Service Level Reports (1431)

- Some administrative changes for authentication did not generate audit events (1440)

- Addressed issue with ASA ACL collection when the reporter can not communicate with all firewalls (1447)

- * Issue with LDAP/TACACS usernames being case sensitive (1458)

- LDAP authentication was not failing over to try other servers (1489)

- Backup method documentation on docs.plixer.com (1506)

- Advanced TCP flag filters using strings would generate log noise (1527)

- Improved performance of Persistent Flow Risk algorithm (1536)

- Developer tasks_view hours filter causes Internal Server Error (500) (1542)

- Dashboards with multiple saved report gadgets cause oops errors (1544)

- Reporting across migrated data and new data doesn’t use the migrated totals tables (1553)

- Migrated totals tables have the wrong scrut_templateid (1556)

- Peak values being less then the total values in the volume -> traffic volume reports (1588)

- Some English values in foreign language themes were out of date (1599)

- New reparser performance (1632)

- Migration from 16.3 mysql to 18.14 removed dashboard gadget permissions (1663)

- LDAP group checking was using sAMAccountName instead of the value specified in the configuration page (1668)

- Map object icons change colors based on polling availability (1691)

- The default group was not being set correctly for new users (1731)

- Payload size preventing CSV rendering of reports (1733)

- Saved reports belonging to users that no longer exist would not show up in report folders (1789)

NOTE: (1458)*

User accounts are no longer case sensitive when being checked on login. If multiple user accounts existed in Scrutinizer prior to the upgrade which were identical except for case, the excess accounts should be deleted from the interface.