Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Product Compatibility

...

Download opReports here - https://opmantek.com/network-management-download/opreports-downloads/


Table of Contents


opReports 3.5.1

Status
subtletrue
colourGreen
titleReleased
22 Feb 2022

Improvements

  • /path/to/omk/conf/opCommon.json has a new setting withdefault being /opreports/on_invalid_hrcachemem_use_only_hrmem=0.
    • With /path/to/omk/conf/opCommon.json set at opreports/opreports/on_invalid_hrcachemem_use_only_hrmem=1,
      opReports attempts to detect situations where invalid hrCacheMemUsed and hrCacheMemSize
      values are being reported that would cause the memory related fields in the Node Health Report to return as negative values.
      • In such a case (detect memory related fields in the Node Health Report would negative values),
        hrCacheMemUsed and hrCacheMemSize will not be used in the calculation of memory related fields
        and a suitable entry to this effect will be logged in opReports.log.
      • This issue has been detected in docker instances where hrCacheMemUsed and hrCacheMemSize values
        were that of the docker host and not that of the docker instance itself.
    • With /path/to/omk/conf/opCommon.json set at opreports/opreports/on_invalid_hrcachemem_use_only_hrmem=0:
      • In such a case (detect memory related fields in the Node Health Report would negative values),
        affected memory related fields will return N/A and a suitable entry to this effect will be logged in opReports.log.
  • The percentile function has been improved:
    • opReports 3.5.1, and newer ,now use the nearest rank inclusive percentile formula as provided in wikipedia:
      https://en.wikipedia.org/wiki/Percentile
    • The differences between the new and old percentile formula cause very few differences in the 95th percentile outputs,
      and when there are differences, they are generally very small fractional changes.

opReports 3.5.0

Status
subtletrue
colourGreen
titleReleased
13 Dec 2021

Improvements

  • Added secrets randomise and secure cookies. For more information see Security Configurations
  • Updated jQuery dependencies.

...

  • Limit the number of sessions per user
  • Lock users that have not logged in in a specified period of time

opReports 3.4.1

RELEASED 16 Mar 2021.

Highlights

This is a maintenance release:

  • 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 3.4.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'.

opReports 3.4.0

RELEASED 01 Oct 2020.

Upgrade Notes

...

This version was released on 16 July 2020.

Highlights

(warning) This release requires updated licenses, please contact Opmantek Support to organise new licenses

  • 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.

...