There are several new features that have been included in this release of IRIS. These include:


  • The ability to view configuration diffs for devices in the graph browser as well as the troubleshooter has been added.
  • Escalation groups can be set up in alarm notifications to send out notifications for alarms that have yet to be acknowledged after a certain period of time.
  • For user reports, certain columns can now be hidden from view, i.e. mnemonics, routers and interfaces.
  • The ability to add SYSLOG and SNMP TRAP rules via the frontend has been added.
  • Column filters have been added to the Device Info Report to improve searching.
  • Options such as copy/bulk delete/column filtering has been added to User dashboards and Reports to be more consistent with rest of IRIS.
  • For the current and suppressed alarms pages, you now have the ability to select multiple alarms and bulk edit/acknowledge/defer them.
  • The ability to filter on the Severity column has been added to the Alarms pages as well as Event Log Search.
  • A few improvements have been done for the Event Log Search page, such as:
    • ability to search across all logs
    • filter events according to view
    • filter according to individual columns
    • additional columns (basetag/device) to improve searching
  • The option to schedule reports on an annual or quarterly basis has now been added.
  • Options to defer alarms for an hour, day, week and forever has been added to the context menu for the alarms pages.
  • The ability to view any notes of devices or mnemonics when right clicking on an alarm has been added to the alarms pages.
  • On the Edit Mnemonics page, the original interface description for a mnemonic gets displayed.
  • In Alarm Notifications, an option “show matches” has been added to indicate which alarms will match and be notified on for the current alarm notification configuration.
  • A “show matches” option has been added to the Matching Rule section (Set Thresholds page) to indicate which elements will match the current threshold configuration.
  • A duration column has been added to the Alarms pages to indicate the total duration of an alarm in one state (ALARM/CLEAR).
  • Configuration diffs can be viewed from the User dashboards.
  • The ability to set a custom ‘from’ address for alarm notification groups has been added.
  • Addition of field for custom emoticon has been added for Slack notifications.
  • The ability match on Device and Mnemonic aliases for threshold breaches has been added.
  • Graph searches have been improved by speeding up db queries with the use of trigram indices.
  • The option to allow notifications to be sent regardless of an alarm being previously in CLEAR state has been added to Alarm Notifications. This allows the ability to notify on alarms that are currently breaching.
  • A rule has been added to display discard and errors graphs for bundled interfaces which are previously hidden in the graph browser and search graphs page.
  • The ability to view historical changes to alarms (i.e. state changes such as alarms being acknowledged/deferred etc. or comments added) has been added. To do so, right-click and select Auditlog.
  • The ability to set the period for how long an alarm stays in flapping status, has been added. This is a backend option, with the current flapping period being set to 30 minutes.
  • An option to set the deferuntil period of alarms has been added. This is used for when a device gets deleted/renamed, where the alarms then get set as deferred until they can be cleaned up. Please note this is a backend option.
  • The ability to disable notification groups from receiving notifications has been added. The option is available in the notification group configuration.
  • A check for device back-up has been added to the Device Check in the device configuration. This is to check whether it is possible to login to the router to be able to perform device config backups.
  • Changes have been made to allow filters set in the graph browser/search graphs page to be remembered upon user login to alleviate the issue of dead elements being displayed by default.
  • An option ‘preserve sorting’ for column sorting in the suppressed alarms widget has been added. This allows the user to save their sorting for the widget. Once ticked, the user can sort by a specific column which will then be remembered.
  • The option to specify a connection method for config backups in the Device Configuration has been added. Depending on which option is ticked, only that method will be used to connect to the device for configuration backups.
  • Validation has been added to the Syslog and SNMP Trap rules to avoid incorrect regex being added.
  • Along with column filtering issues being fixed for the Search Event Logs page, the ability to filter on all fields available on the frontend has been added to the Iris API.
  • A new API call has been added to allow users to pull graph data for specific intervals specified via the ‘step’ parameter. Here is an example of a call:

            This will return graph data in 5-minute intervals for the period specified.

  • The ability to set maintenance periods for views (including all sub-views) and devices, as well as set a global maintenance period, has been added which allows users to exclude stats retrieved in this period in User Reports. Please note/; alarms/notifications of a view/device in maintenance will still trigger/notify. 
  • The ability to successfully run a network discovery for SNMP v3 devices has been added.
  • When queries are being executed on the flow explorer page, the graph will now display “loading” while busy and return a message of “no data to display” if there isn’t any data available for the time period selected.
  • For the flow explorer page, columns have been added to display the mnemonics for inbound/outbound interfaces.
  • The ability to specify a time of when scheduled Daily reports run has been added. 


Bug fixes:

  • The issue where the alarm notification descriptions didn’t display in mail notifications has been fixed.
  • Graph errors caused null.rrds have now been resolved - these should not display anymore.
  • Alarm notifications set to trigger for source “Any” wasn’t sending out notifications. This has now been resolved.
  • The issue of exporting flow data to PDF from the troubleshooter has been fixed.
  • Resetting the graph in the troubleshooter (click `Reset`) wasn’t changing the time frame set. Clicking reset now defaults a time frame of a day.
  • Incorrect failure statuses for device checks from the Graphs Browser has been fixed.
  • The issue with discover processes causing high CPU/load has been resolved.
  • The issue with backup configurations not displaying for Cisco Nexus devices has been fixed.
  • Graphs now order correctly according to their rank value on the graph search page.
  • The issue where Pertinent Configs of a device wasn’t displaying in the troubleshooter has now been fixed.
  • The issue where thresholds set to match on a specific view still creates alarms for other views that the element is in, has been fixed.
  • The topology page now gets filtered according to view when logging in with view-restricted user. 
  • When creating a new track flow query based on filters added, not all filters such as interface, port, ASN etc. got added. This has been fixed.
  • The issue where acknowledging an alarm on the current alarms page acknowledges all alarms of the same basetag, has been fixed.
  • The issue where graphs of mnemonics with aliases set displayed the mnemonic name instead of the alias, has now been fixed.
  • The issue where widgets overlapped in the dashboard has been fixed by adding the ability to scroll horizontally.
  • When changing a hostname of a device, the old hostname did not get cleaned up causing the “change pending” state to remain in the device’s configuration. This has been solved along with cleaning up the graphs of the old hostname once the change has been completed. Please note that this requires dbsyncd to run and complete after the name change as well as the graphs needing to be created.
  • When alarms CLEAR outside of business hours (of a view that has the option ‘defer outside of BH’ is set), the ticket status gets set to DEFER. These alarms then get set to NEW when business hours start, which is incorrect. This has been fixed - CLEAR Alarms will remain with ticket_status = CLEAR.