Product Compatibility

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

Download opHA here - https://opmantek.com/network-management-download/opha-downloads/

For opHA 4, see opHA 4 Release Notes.

Introduction

...

• The Primary is the server that keeps the information of all the pollers and it is where we can read all the information from.
• The pollersPollers, collect their own data, and send that information to the Primary when it is requested. 

...

The first time the pull script runs, it requests all the data for each configured poller. Next time, it requests only the modified data since the last synchronisation. 

Releases

3.6.

...

2

Big release with an upgraded GUI framerwork to deliver accessibility enhancements and dark mode.

...

8th March 2023

• An opHA peer will now unlock itself after 15 mins. use opha_max_lock in opCommon.json to change this timeout.
  
• In the peer GUI it now shows if the peer is locked and you have the option to unlock this from the GUI.
• opha_allow_insecure has been implemented across the whole application.
  
• Fix issue where a peer would show a stale status message when the primary role has been changed.
• Gui fixes for the peers view.
• Debug messages improved for the cli.

3.6.1

Fixed issue where the function in the gui and cli sync-all-nodes would not use the opha_allow_insecure config option.

3.6.0

Big release with an upgraded GUI framework to deliver accessibility enhancements and dark mode.

• This release includes improved Accessibility options, including support for Dark Mode. We have taken the opportunity while we tidied up the screens to change Opmantek to FirstWave. These are new features that are backward compatible with earlier releases.

• Fixed issue where Perl would throw a warning about ../Mojo/Asset/Memory.pm

3.5.2

Support for MongoDB 4.2 please see Upgrading to MongoDB 4.2

Changed the installer to not touch the server role if it was already been set in opCommon.json

3.5.1

This was an internal release

3.4.3

...

• Desynchronisation of events: Now the delete events cron job can be removed and run after the pull events when delete_events=true is passed as a parameter to the pull job.
• Improve error handling in Nodes API.
• Centralised Distribution of Node Configuration by opHA
• New API to send configuration items
• opHA will distribute the API Key when it is a primary and encryption is set. 
• ! Important note: After upgrading to opHA 3.4.3 the role will be set to Standalone, you will need to Set Role to restore the role. 

3.4.2

...

• Updated core dependencies
• Cookies now support samesite strict, see Security Configurations

3.3.3-1

...

The new upcoming release of opHA 3 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

3.1.2

...

• Bugfix: Discover peer window was closing when required fields missing. 
• Bugfix: Update the last_update field to the synchronisation. This was causing some data not being updated in the Primary and expire_at field for events not being updated in all the documents. 
• New cli cleanup functions to clean data from the cli tool.
• Added new cli function get_status to get the status for each poller in json format. 
• Some minor bug fixes and internal improvements. 

...

• Added new features to the centralised configuration from the Primary with support for OMK and NMIS files:
  • Added new configuration file types. 
  • Remove files from pollers. 
  • Add a button with rollback instructions. 
  • Improved landing page, with information of the peers. Now the peers have an status API that check the daemons and the database status.
  • Send the role to the pollers: If a role is set to poller, it doesn't let the use to use the GUI functions. 
  • Add conf.d to support zip. 
  • opha new cleanup functions. 
  • View resulting configuration files. 

3.0.5 

Status
colour Yellow title beta

...