Page tree
Skip to end of metadata
Go to start of metadata

opReports 2.6.1

Version 2.6.1 was released on 20 Feb 2015.


This is primarily a maintenance release, but two new features were added:

  • The new report  type "Interface Utilisation" was added. It allows you to select utilisation thresholds and exceedence counts for flagging an interface as over-limit, and provides a means for selecting many nodes and interfaces in bulk. This report is available both in HTML and CSV form.
  • opReports 2.6.1 ships with the opReports scheduler, which allows the scheduling of reports to generae (and all their parameters) for future execution. There is also an experimental feature for "remote controlling" NMIS so that only the specified nodes and interfaces are collected, and only for the configured time period of the report.
    Please note that the opReports scheduler is still under active development, currently supports only scheduling of "Interface Utilisation" reports, and that its configuration format might change. We plan to fine-tune and expand the scheduler's capabilities for the next opReports releases.

opReports 2.6.0

Version 2.6.0 was released on 24 Nov 2014


This release is primarily a maintenance release, introducing just one major new feature:

  • opReports now support Quality of Service reporting for Huawei devices (if used with NMIS 8.5.4G or newer).
  • The node report was improved and now properly supports user-selectable reporting periods
  • Bandwidth and interface speed figures are now displayed in a more human-friendly form.

opReports 2.6.0 requires NMIS 8.5G for correct operation in general, and 8.5.4G or newer for Huawei QoS reporting

opReports 2.5.7

Version 2.5.7 was released on 13 Jun 2014.


This release is primarily a compatibility release:

  • opReports is now also compatible with NMIS version 8.5G.
  • opReports no longer leaves behing unnecessary debug output in files in /tmp.
  • The node report now includes graphs for error packets regardless of the node's model support standard or high-capacity counters (older releases only covered standard counters).

opReports 2.5.6

Version 2.5.6 was released on 4 Mar 2014.


This release contains primarily bug fixes and minor improvements:

  • The command-line help text was improved.
  • The Quality of Service reports was updated to include the Maximum PrePolicy Utilization measure.

opReports 2.5.5

Version 2.5.5 was released on 26 Feb 2014.


This release contains primarily bug fixes:

  • The Quality of Service report has been improved for better robustness. A minor model update in NMIS is required to support the new capabilities of opReports.
  • The Node Health report has been improved and displays misconfigured nodes or nodes with no statistic data in a more consistent fashion.
  • The Node Health report now supports devices that have Cisco-style CPU statistics but none or only partial memory data.
  • Some unnecessary debug output has been removed.
  • The computation of the 95th percentile of CPU utilization has been improved for greater robustness.

opReports 2.5.4

Version 2.5.4 was released on 21 Feb 2014.


This release contains a number of bug fixes and minor improvements:

  • The Response Time report now works with group selectors.
  • Improvements were made to the display of nonreachable or misconfigured nodes, where no or only partial statistics are available
  • The link to the CPU graph is no longer shown if the device in question does not support CPU statistics.
  • Support for Teldat devices has been improved, and memory statistics are now presented for these devices.
  • The licensing system has been updated: to evaluate opReports you will require a new evaluation license. Full licenses are not affected by this change.

opReports 2.5.3

Version 2.5.3 was released on 7 Feb 2014.


This release introduces no major new features but fixes a number of bugs and imperfections.

  • A bug in the display of  interface average error and discards was fixed, which caused these measures to come up incorrectly as 0.0% under certain circumstances.
  • The computation of memory and CPU utilisation measures was completely overhauled and is substantially more robust now, e.g. dealing with a node whose memory has been increased on the go.
  • Some computational inefficiencies have been removed and opReports should run slightly faster now.
  • CPU stats are now computed for all devices whose models support CPU statistics, not just a subset based on known model names as before.

opReports 2.5.2

Version 2.5.2 was released on 4 Feb 2014.


  • Archival of reports has been improved.
    The standard cron scripts now create all report types (except Node) in HTML and CSV format, and the view archive page presents access links for both formats where applicable.
  • Improved support for asymmetric interface speeds
    The reports now perform appropriate utilization computations if different Interface Speed In and  and Interface Speed Out settings are given for a device.
  • The Response Time report now deals correctly with nodes that have the ping node configuration option set but not collect.

opReports 2.5.1

Version 2.5.1 was released on 31 January 2014.


This release incorporates a number of features requested by Opmantek commercial customers, and a variety of bug fixes.

  • There is one new report type, Response Time, with configurable exception threshold
    (see response_exception_threshold in opReports.nmis
  • All report types (except type Node) now offer exporting as CSV.
    This option can be selected in the GUI as well as on the command line (using the argument format=CSV).
  • The Node report now also supports node selection by regular expression.
  • The Node Health report now includes more metrics related to maximum CPU and memory usage.
  • The QoS report now includes more measurements related to post-policy resource utilization.

opReports 2.4.1

Version 2.4.1 was released on 4 Dec 2013.


  • All the reports that allow multiple nodes now let you also select the nodes by regular expression.
  • The reports now allow both business hour reporting as well as after hours reporting.
  • The date handling has been improved; you can now supply any two of start date, end date and reporting days and opReports figures out the rest.
  • The wan report now supports user-selectable detail levels and a few new measures that can be reported (eg. 95th percentile for utilization and others)
    This feature is described in more detail on the page opReports detail levels for WAN reports.
  • The node health report now includes the 95th percentile for cpu and memory use.
  • No labels