Date: Fri, 29 Mar 2024 14:43:39 +0000 (UTC)
Message-ID: <562075730.4171.1711723419873@skald.opmantek.com>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_4170_562001732.1711723419872"
------=_Part_4170_562001732.1711723419872
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Refer to product compatibility to determine =
supported Operating Systems and Database Versions.
Download opReports here - https://opmantek.com/network-management-download/opreports-downloads/=
opReports 4.5.4
RELEASED 30 Jan=
uary 2024
Improvements
- Added support for Debian 11 to the installer
opReports 4.5.3
RELEASED 22 November 2023
Improvements
- Fixed a bug "No report with this ID exists!" when editing an entry in <=
a href=3D"/display/opReports/Scheduling+Reports">Report Schedules view.=
- Enhance Node Health Report to use the alternate memor=
y and CPU MIBS for Cisco devices (ciscoMemory.pm plugin version 2.0.3 or higher is required to make repo=
rts 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
Improvements
- In Burst Billing report make the Field Description in the Layout tab vi=
sible. If text is entered here, the D=
escription column will be included in the report and will display this text=
in each row of the report.
opReports 4.5.1
RELEASED 27 April 2023
Improvements
- Added Exception Reporting to Response Time Report. When creating the Re=
sponse Time Report, in the Layout tab, set Show Exceptions Only to true. Se=
e Response Time Re=
port
- opReports now uses Opmantek grid instead of data tables for Saved Repor=
ts and Operational Status pages. The grid provides better filter functional=
ity, pagination and a custom filter which allows the user to select the num=
ber 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.
opReports 4.5.0
RELEASED 23 Nov=
ember 2022
Big release with an upgraded GUI framework to deliver accessibility enha=
ncements and dark mode.
Improvements
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-Dem=
and Reports.
- One-Off Reports are generated from the Views >> Report Sc=
hedules page using the Create one-off Report butt=
on.
- The generated reports previously displayed on the Views >>=
; On-Demand page are now displayed on the Views >> S=
aved Reports page as category once-off.
- The generated One-Off Reports are also displayed on the Views &=
gt;> Saved Reports page as category once-off.<=
/li>
- The generated Scheduled Reports are also displayed on the Views >>=
; Saved Reports page as category recurring.
opReports 4.3.0-1
RELEASED =
1 February 2022
Highlights
This is a patch release:
opReports 4.3.0
RELEASED 1 Dece=
mber 2021
Highlights
This is a maintenance release:
opReports 4.2.1
RELEASED 18 Mar 2021<=
/span>
Highlights
This is a maintenance release:
- Introduces extra debug=3D9 level =
logging to assist in researching issues when encountered in opReports.
- Fixes 9=
5th Percentile calculation in =
WAN Utilisation Distribution Report and&=
nbsp;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, St=
andardised Quality of Service supported devices that do not suppor=
t CBQoS will display inte=
rface QoS even though the interface has a setting of 'collect=3Dfalse'.
opReports 4.2.0
RELEASED 30 Sept 2020=
Upgrade Notes
The new upcoming release of opReports 4 will work on Opmantek's latest a=
nd fastest platform, however, the currently installed products are incompat=
ible with this upgrade.
To find out more about this upgrade please read: Upgrading Opmantek Applications
opReports 4.1.1
RELEASED 29 July=
2020
Highlights
This version:
requires updated licenses, please contact Opmantek Support to organi=
se new licenses
Contact Opmantek Support should be a link to:
https://opmantek.com/support/c=
ontact/
- makes the following improvements:
- QoS Report:
- Model =
;and Vendor det=
ails 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 orig=
inal behaviour of only returning nodes according to opCommon configuration =
settings:
- where uptime is shorter than
uptime_sho=
rtest_days
(default 7); or
- where uptime is longer than
uptime_longest_days
(default 365).
- When 'Exceptions Report=3Dfalse', t<=
span>he Uptime Report provides a third column with the remainder of nodes t=
hat have an uptime to report,
in other words, those with uptime f=
rom uptime_shortest_days
to
uptime_longest_days
.
- Please read Generating Reports for generating on-demand reports: this n=
ew option is uptime_exceptions on t=
hat page.
- New paragraph Requirements in opReports document=
ation for each of the following Reports:
opReports 4.1.0
RELEASED 24 June 2020
=
This release requ=
ires updated licenses, please contact Opmantek Support to organise new licenses
- opReports version compatible with NMIS 9.
- JSON Configuration files: The .nmis configuration file=
s 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 req=
uires a License update due to the new license structure.
- Workaround:
- If Node Report in opReports 4.1.0 does not display graphs, then NMIS9 i=
s most likely missing the entry for 'rrddraw' under 'files' in nmis=
9/conf/Config.nmis
'files' =3D> {
'nmis' =3D> '<cgi_url_bas=
e>/nmiscgi.pl',
'rrddraw' =3D> '<cgi_url_base>/rrddraw.pl',=
code>
'network' =3D> '<cgi_url_base>/network.pl',
<=
br>'node' =3D> '<cgi_url_base>/node.pl',
'ev=
ents' =3D> '<cgi_url_base>/events.pl',
'logs' =3D&=
gt; '<cgi_url_base>/logs.pl',
'outage_file' =3D> '=
<nmis_conf>/outage.dat',
'nmis_log' =3D> '<nmis=
_logs>/nmis.log',
'fping_log' =3D> '<nmis_logs>=
/fping.log',
'auth_log' =3D> '<nmis_logs>/auth.log=
',
'polling_log' =3D> '<nmis_logs>/polling.log',=
code>
'syslog_log' =3D> '<nmis_logs>/cisco.log',
'event_log' =3D> '<nmis_logs>/event.log',
=
'nmis_favicon' =3D> '<menu_url_base>/img/nmis_favicon.png',
=
'nmis_home' =3D> '<menu_url_base>/img/home.png',
<=
br>'nmis_help' =3D> '<menu_url_base>/img/question.png',
'nmis_slave' =3D> '<menu_url_base>/img/slave.png',
'company_logo' =3D> ''
},
------=_Part_4170_562001732.1711723419872
Content-Type: image/svg+xml
Content-Transfer-Encoding: 7bit
Content-Location: file:///C:/4f0cbb478c12786637310c851e24264c