...

opReports 4.5.3

RELEASED 22 November 2023

Improvements

...

• Fixed a bug "No report with this ID exists!" when editing an entry in Report Schedules view.
• Enhance Node Health Report to use the alternate memory and CPU MIBS for Cisco devices (ciscoMemory.pm plugin version 2.0.3 or higher is required to make reports work).
• Added a

...

• new report  Node Health Disk Metrics Report. This report adds disk metrics related to disk storage. You can access this report under Special Reports.

opReports 4.5.2

RELEASED 27 July 2023

...

opReports 4.4.1

RELEASED 14 September 2022.

Highlights

This is a maintenance release:

...

opReports 4.4.0

RELEASED 18 July 2022.

Highlights

This is a maintenance release:

...

opReports 4.3.1

RELEASED 25 May 2022.

Highlights

• On-Demand Reports have been deprecated.
  • One-Off Reports are the replacement for On-Demand Reports.
  • One-Off Reports are generated from the Views >> Report Schedules page using the Create one-off Report button.
  • The generated reports previously displayed on the Views >> On-Demand page are now displayed on the Views >> Saved Reports page as category once-off.
  • The generated One-Off Reports are also displayed on the Views >> Saved Reports page as category once-off.
  • The generated Scheduled Reports are also displayed on the Views >> Saved Reports page as category recurring.

opReports 4.3.0-1

RELEASED 1 February February 2022.

Highlights

This is a patch release:

...

opReports 4.3.0

RELEASED 1 December 2021.

Highlights

This is a maintenance release:

• 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

opReports 4.2.1

RELEASED 18 18 Mar 2021.

Highlights

This is a maintenance release:

...

Upgrade Notes

The new upcoming release of opReports 4 will work on Opmantek's latest and fastest platform, however, the currently installed products are incompatible with this upgrade. 
To find out more about this upgrade please read: Upgrading Opmantek Applications

...

Highlights

This version:

• 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

...

• 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' => ''
},