Product Compatibility

Refer to product compatibility to determine supported Operating Systems and Database Versions.

...

opReports 4.6.1

• The opreports-sftp.pl script has been updated to include improved error handling. The script will now exit with a failure status on encountering errors, ensuring more reliable and consistent behavior during file transfers.
• The new Post Report Script feature has been updated to allow a Post Report Script to be run after any report. 
• The handling of the Post Report Script has been updated. In previous versions, the opreports-sftp.pl script would automatically run whenever the a report was generated. Now, this behavior has been changed to give users more control. Users must now manually select the opreports-sftp.pl script from a dropdown menu in the Advanced tab of opReports if they want it to execute after a report is generated. The script will only run if it is explicitly chosen by the user. See  Migration in Automatically copy opReports to another server using SFTP.
• The opreports-sftp.pl script and the Post Report Script have a new configuration parameter: opreports_post_report_script_timeout. This parameter allows users to specify a timeout duration for the post report script. By setting this parameter in opCommon.json, users can control the maximum amount of time the post-report script is allowed to run, ensuring that it doesn't hang indefinitely or run longer than expected. See Post Report Script.

opReports 4.6.0

• Added support for MongoDB 6.0 please see Upgrading to MongoDB 6.0

opReports 4.5.4

...

Released   30 January 2024

Improvements

...

• In Burst Billing report make the Field Description in the Layout tab visible. If text is entered here, the Description column will be included in the report and will display this text in each row of the report.

opReports 4.5.1

...

• Added Exception Reporting to Response Time Report. When creating the Response Time Report, in the Layout tab, set Show Exceptions Only to true. See Response Time Report
• opReports now uses Opmantek grid instead of data tables for Saved Reports and Operational Status pages. The grid provides better filter functionality, pagination and a custom filter which allows the user to select the number of rows to be displayed in the grid.
• Fixed a bug in Traffic Snapshot Report where it was not displaying any Business Services to choose from.

...

• Burst Billing reports ported from opReports 3.5.2 and added functionality to support opCharts Element Lists
  • Burst Billing Report
  • Bandwidth Exceeds Contract Report
• Added support for these two reports to call a script after they are finished.

...

• GPON Port Capacity Report (modeled on Interface Capacity Report) now provides 'ONT Description' correctly.
• GPON Port User Traffic Report (modeled on Traffic Usage Report) now provides 'ONT Description' correctly.

...

• New GPON Port Reports which support Node and GPON Port List File:
  • GPON Port Utilisation Report (modeled on Interface Utilisation Report)
  • GPON Port Capacity Report (modeled on Interface Capacity Report)
  • GPON Port User Traffic Report (modeled on Traffic Usage Report)
• Cookies now support samesite strict, see Security Configurations
• Fixed issue in checkdaemons.sh with stopping mongodb

...

• Introduces extra debug=9 level logging to assist in researching issues when encountered in opReports.
• Fixes 95th Percentile calculation in WAN Utilisation Distribution Report and WAN Utilisation Distribution Summary Report:
  Prior to version 4.2.1 the reflected value for 95th Percentile should be multiplied by 8 to get the correct value for 95th Percentile in the above-mentioned reports.
• In the QoS Report, Standardised Quality of Service supported devices that do not support CBQoS will display interface QoS even though the interface has a setting of 'collect=false'.

...

• requires updated licenses, please contact Opmantek Support to organise new licenses

  Contact Opmantek Support should be a link to:
  https://opmantek.com/support/contact/
  
  

• makes the following improvements:
  • QoS Report:
    • Model and Vendor details are provided per node in the report.
  • Uptime Report:
    • New option 'Exceptions Report' (Default: true)
      
      
      • The Uptime Report now offers this new option which defaults to the original behaviour of only returning nodes according to opCommon configuration settings:
        • where uptime is shorter than uptime_shortest_days (default 7); or
        • where uptime is longer than uptime_longest_days (default 365).
      • When 'Exceptions Report=false', the Uptime Report provides a third column with the remainder of nodes that have an uptime to report,
        in other words, those with uptime from uptime_shortest_days to uptime_longest_days.


      • Please read Generating Reports for generating on-demand reports: this new option is uptime_exceptions on that page.
  • New paragraph Requirements in opReports documentation for each of the following Reports:
    • Traffic Snapshot Report
    • Monitored Services Report
    • Node Report

...

Image Added This release requires updated licenses, please contact Opmantek Support to organise new licenses

• opReports version compatible with NMIS 9.
• JSON Configuration files: The .nmis configuration files will be replaced by .json files. 
• New License 2.0 structure used. 
• ! Important notice: Due to the JSON configuration files upgrade, when updating to this version, upgrade of all OMK Products installed will be required (Not NMIS) to at least X.1. version. It also requires a License update due to the new license structure. 
• Workaround:
  • If Node Report in opReports 4.1.0 does not display graphs, then NMIS9 is most likely missing the entry for 'rrddraw' under 'files' in nmis9/conf/Config.nmis
    • 'files' => {
'nmis' => '<cgi_url_base>/nmiscgi.pl',
'rrddraw' => '<cgi_url_base>/rrddraw.pl',
'network' => '<cgi_url_base>/network.pl',
'node' => '<cgi_url_base>/node.pl',
'events' => '<cgi_url_base>/events.pl',
'logs' => '<cgi_url_base>/logs.pl',
'outage_file' => '<nmis_conf>/outage.dat',
'nmis_log' => '<nmis_logs>/nmis.log',
'fping_log' => '<nmis_logs>/fping.log',
'auth_log' => '<nmis_logs>/auth.log',
'polling_log' => '<nmis_logs>/polling.log',
'syslog_log' => '<nmis_logs>/cisco.log',
'event_log' => '<nmis_logs>/event.log',
'nmis_favicon' => '<menu_url_base>/img/nmis_favicon.png',
'nmis_home' => '<menu_url_base>/img/home.png',
'nmis_help' => '<menu_url_base>/img/question.png',
'nmis_slave' => '<menu_url_base>/img/slave.png',
'company_logo' => ''
},

...