---
title: "Geneos Upgrade Notes"
description: ""
url: "https://docs.itrsgroup.com/docs/all/geneos/geneos-upgrade-notes/index.html"
---
## Overview

This document provides information about the product changes that can affect upgrading from one version of Geneos to another.

To learn more about the supported Geneos versions and new features in the Geneos 7.x release, see the following documents:

- [Geneos 7.x Release Notes](https://docs.itrsgroup.com/docs/all/geneos/7x-geneos-release-notes/index.html)
- [Geneos 7.x Compatibility Matrix](https://docs.itrsgroup.com/docs/all/geneos/7x-geneos-compat-matrix/index.html)
- [What's New in Geneos](https://docs.itrsgroup.com/docs/all/whats-new/geneos-whats-new/index.html)


**Critical Update**

 From February 2026, ITRS is introducing a new license file format, which requires the Licence Daemon to be upgraded to version 7.8.0 or later. Support for Licence Daemon versions earlier than 7.8.0 will end on 31 July 2026.

We strongly recommend upgrading your Licence Daemon ahead of time. Refer to the [upgrade notes](https://docs.itrsgroup.com/docs/all/geneos/geneos-upgrade-notes/index.html#changes-in-licence-daemon-reporting-and-license-files) for full details and required actions, and contact [ITRS Support](mailto:support@itrsgroup.com) to obtain a new license file. 


## Upgrade to Geneos 7.12.x

### Disk plugin totalSpace includes reserved space

Starting with Geneos 7.12.0, the Disk plugin publishes `totalSpace` as filesystem capacity (`f_blocks`), including space reserved for the root user. This aligns with the `Size` value reported by `df`. Previously, `totalSpace` excluded that reserved space.


**Important**

 On Unix-like systems, when you upgrade Netprobe, `totalSpace` typically adjusts once by approximately the reserved amount. Historical charts will show that one-time change, and rules or thresholds that use `totalSpace` may need review. `freeSpace` and `percentageUsed` are unchanged.

Review any rules, thresholds, dashboards, or published attributes that use `totalSpace`. For metric definitions, see [Disk](https://docs.itrsgroup.com/docs/geneos/current/collection/disk/index.html). 


## Upgrade to Geneos 7.11.x

### RHEL 8 uses the generic Linux packages

Starting with Geneos 7.11.2, the dedicated RHEL 8 packages for Gateway and Netprobe are no longer provided. Dedicated RHEL 8 binaries are replaced with the generic Linux binaries so that RHEL 8 deployments can take security fixes that ship only in the generic packages. This includes an update of the `libcurl` library to version 8.21.0 to address the security vulnerability **CVE-2026-8924**.

To run these components on RHEL 8, download and install the generic Linux x86-64 packages.


**Important**


The generic packages have different library requirements from the dedicated RHEL 8 packages. Some RHEL 8 hosts may need the `libnsl` package. See the required libraries for [Gateway](https://docs.itrsgroup.com/docs/geneos/current/processing/gateway_installation_guide/index.html#required-libraries) and [Netprobe](https://docs.itrsgroup.com/docs/geneos/current/collection/netprobe/installation/quickstart-linux-and-other-platforms/index.html#library-dependencies).



### MDM Exegy feed adapter requires XTP firmware 4.16+


**Breaking change**

 Geneos 7.11.0 requires Exegy XTP appliance firmware version 4.16 or later for the MDM Exegy feed adapter to work. 


Exegy considers XTP firmware version 4.11.x and earlier retired. Exegy strongly recommends upgrading older appliance firmware for continued support and access to newer features.

Before upgrading to Geneos 7.11.0, verify that your Exegy XTP appliances are running firmware 4.16 or later. If your appliances are running firmware 4.11.x or earlier, upgrade the appliance firmware before upgrading Geneos.

For more information, see [Exegy adapter](https://docs.itrsgroup.com/docs/geneos/current/collection/mdm-feed-adapter/index.html#exegy-adapter).

## Upgrade to Geneos 7.10.x

### Collection Agent plugins require Collection Agent version 6.6.0

Upgrading the following Collection Agent plugins to these versions requires Collection Agent 6.6.0 or later because of dependency updates introduced in that version:

- AWS Collection Agent plugin version 6.5.0
- Azure Monitor Collection Agent plugin version 6.6.0
- Google Cloud Platform Collection Agent plugin version 6.3.0
- Kubernetes Collection Agent plugin version 6.5.0
- Prometheus Collection Agent plugin version 6.5.0

## Upgrade to Geneos 7.9.x

### SSO idle auto logout

Active Console 7.9.0 introduces automatic logout for idle SSO users to enhance security. This feature monitors user activity and automatically logs out SSO users after a period of inactivity.


**Important**

 In version 7.9.0:

- SSO users are automatically logged out after 30 minutes of inactivity.
- A warning dialog is displayed 60 seconds before logout, giving users the option to stay logged in.
- SSO credentials are cleared after use.

Starting with Active Console 7.9.2, these settings are disabled unless explicitly defined.

Review the settings below to adjust these behaviors and avoid unintended logout or loss of credentials. 


| Flag | Description | Active Console 7.9.0 behavior | Active Console 7.9.2 behavior |
| --- | --- | --- | --- |
| `ssoIdleAutoLogoutTime` | Specifies the idle timeout in seconds before an SSO user is automatically logged out. | If not defined, defaults to `1800` seconds (30 minutes). Set to `0` to disable. | If not defined, the setting is disabled. |
| `ssoIdleShowWarningTime` | Specifies when to display a warning dialog before the SSO idle logout occurs. | If not defined, defaults to `60` seconds. Set to `0` to disable. | If not defined, the setting is disabled. |
| `autoClearSSOCredentials` | Controls whether the SSO username and password fields are cleared after use. | If not defined, defaults to `true`. | If not defined, the last entered credentials are cached. |

These settings can be configured in the `ActiveConsole.gci` file or via command-line arguments. For detailed configuration options, see [Active Console startup settings](https://docs.itrsgroup.com/docs/geneos/current/visualization/active-console/configuration/startup-settings/index.html#activeconsoleexe-flags).

## Upgrade to Geneos 7.8.x

### Netprobe and Gateway 7.8.x introduce row limits for Dynamic Entity dataviews


**Breaking change**

 A default row limit of 200 rows is now enforced for Dynamic Entity dataviews where no limit was previously configured. 


Row limits remain fully configurable in the Gateway Setup Editor but are no longer unbounded by default. Dynamic Entity dataviews could previously return large numbers of rows when no limit was set and cause performance degradation of the Gateway or the Active Console.

Both the Netprobe and Gateway must be at least version 7.8.0 to apply this row limit configuration. For more information, see [Collection Agent parameters](https://docs.itrsgroup.com/docs/geneos/current/processing/configuration/dynamic_entities/index.html#collection-agent-parameters-configuration).

This change introduces safer defaults while preserving existing configurations. Review your monitoring setup and explicitly configure higher row limits where larger result sets are needed. For row limits on other plugins, see [Netprobe and Gateway 7.7.x introduce row limits for dataviews](#netprobe-and-gateway-77x-introduce-row-limits-for-dataviews).

### Changes in Licence Daemon reporting and license files

Geneos 7.8.0 introduces an enhanced Licence Daemon as part of the wider Geneos 7 improvements aimed at simplifying operations and improving product insight. As part of this change, a new license file format is being introduced, which requires upgrading the Licence Daemon to version 7.8.0 or later.

Key changes:

- Licence Daemon versions earlier than 7.8.0 will reach end of life on 31 July 2026. These will no longer be supported or available for download from the ITRS Resources website.
- Licence Daemon 7.8.0 and later require a new license file format. License files issued for versions earlier than 7.8.0 are not compatible with Licence Daemon 7.8.0 and later, and license files issued for 7.8.0 and later are not compatible with Licence Daemon versions earlier than 7.8.0.
- License usage is now automatically written to a weekly-updated, encoded report file containing the full history of licence usage. You can also control where license usage reports are stored.
- The Licence Auditor is no longer required. License usage can now be shared by sending the automatically generated license report file to ITRS, eliminating the need for manual auditing.
- Summary and detailed CSV downloads of licence usage are no longer available from the Licence Daemon web page, as reporting is now handled via the generated report files.

Follow the required actions below:
- Contact ITRS Support or your account manager to obtain a new license file compatible with 7.8.0 and later.
- Plan and complete the upgrade to Licence Daemon 7.8.0 or later.

## Upgrade to Geneos 7.7.x

### Netprobe and Gateway 7.7.x introduce row limits for dataviews


**Breaking change**

 A default row limit of 200 rows is now enforced for certain plugins where no limit was previously configured. 


When upgrading the Netprobe and the Gateway to version 7.7.0 or later, a default row limit is enforced for the following plugins. This change only applies where no row limit has been configured for the sampler.

- Netprobe plugins:

  - API
  - Dynamic Entities Health
  - REST API
  - SQL Toolkit
  - Toolkit
  - Trapmon
  - WMI

- Gateway plugin:

  - Gateway-SQL

If a plugin already has a row limit explicitly configured, its behavior is unchanged. If no row limit was previously set, a new default limit of 200 rows is now applied. In such cases, the sampling status will display a warning such as `WARNING: Row limit of 200 reached. Not all rows are being displayed.`

Row limits remain fully configurable but are no longer unbounded by default. Some plugins could previously return large numbers of rows when no limit was set and cause performance degradation of the Gateway or the Active Console.

This change introduces safer defaults while preserving existing configurations. Review your monitoring setup and explicitly configure higher row limits where larger result sets are needed.

### TLS version default updated to 1.2

The default minimum TLS version for the following Geneos components is now 1.2.

- Gateway
- Netprobe
- FIX Analyser 2 Netprobe
- File Agent
- Licence Daemon
- Webslinger

This change improves security by preventing the use of deprecated and vulnerable TLS versions (TLS 1.0 and TLS 1.1) by default.

This may affect connections to older systems or services that do not support TLS 1.2 or higher. If you need to maintain compatibility with systems that only support TLS 1.0 or TLS 1.1, you can override the default by setting the `-minTLSversion` command line argument to the TLS version you need to use. However, this is not recommended due to security vulnerabilities in these TLS versions.

## Upgrade to Geneos 7.6.x

There are no breaking changes when upgrading to Geneos version 7.6.0.

## Upgrade to Geneos 7.5.x

### Manual provision of jConnect JDBC driver required for Sybase historical charts

To generate historical charts using Sybase, you must now manually supply the jConnect JDBC driver file to your Active Console installation. This driver is no longer included with the Active Console package.

For detailed instructions and supported driver versions, refer to the [Active Console database support documentation](https://docs.itrsgroup.com/docs/geneos/current/visualization/active-console/system-requirements/index.html#supplying-the-jconnect-jdbc-driver-for-active-console).

## Upgrade to Geneos 7.4.x


**Release Withdrawn**


Geneos versions 7.4.0 and 7.4.1 have been withdrawn and are no longer available for download due to a discovered memory leak.

We recommend upgrading to Geneos version 7.4.2. This release includes the fix for the issue, along with the new features and bug fixes previously introduced in the withdrawn Geneos versions 7.4.0 and 7.4.1.

For more information on the components packaged with this release, refer to the [Geneos 7.x Release Notes](https://docs.itrsgroup.com/docs/all/geneos/7x-geneos-release-notes/index.html).



### Collection Agent backward compatibility

This release introduces backward compatibility to ensure that the Collection Agent packaged with Netprobe 6.x versions functions correctly with Gateway version 7.4.x.

If you are using the Collection Agent packaged with Netprobe 6.x with Gateway versions 7.0.x to 7.3.x, upgrade to Gateway 7.4.0 to prevent Collection Agent startup failures.

## Upgrade to Geneos 7.3.x

### Geneos PCRE2 upgrade

The Geneos PCRE library has been upgraded to PCRE2 10.44 for improved regular expression handling. This may introduce breaking changes to your setup as this update affects multiple plugins (for example, FKM, FTM, and FIX Analyser) and Gateway features, like Database Logging and Gateway plugins, that use regular expressions. It is recommended to review and test your existing regex configurations to ensure compatibility with PCRE2.

### Renamed XML files in the Gateway templates directory

Template files for the Azure and Remote RTDS Collection Agent plugins have been renamed for clarity. This may introduce breaking changes if you are referencing the absolute or relative path of the template files in your setup. Review and update your setup as needed to reference the updated filenames.

### New VMware Collection Agent plugin configuration

If you are using the VMware Collection Agent plugin, upgrading to Geneos version 7.3 requires you to create a new configuration. Configuration files from older versions are no longer compatible.

### Geneos OpenSSL upgrade

Beginning version 7.3.1, OpenSSL in Geneos has been upgraded from version 1.1.1w to version 3.4.1 to support ongoing security updates and enhanced compatibility. Ensure that your system libraries and dependencies are compatible with OpenSSL 3.4.1 to avoid runtime issues. Additionally, if you are using Geneos on generic Linux systems, be aware that the Kerberos implementation has been transitioned from Heimdal Kerberos to MIT Kerberos.

## Upgrade to SSO Agent 1.16

### SSO Agent required Java version

The SSO Agent has been upgraded to version 1.16, which now requires Java 17 as the minimum supported version. This may require you to upgrade the Java version on your machines running the SSO Agent.

## Upgrade to Geneos 7.2.x

### Display columns in the FKM plugin

Beginning with version 7.2.x, the **fileSize** and **laggingSize** columns now display in KiB (kibibytes) instead of Kb (kilobytes) and in B (bytes) instead of b (bits), while **updateRate** is now displayed in KiB/s (kibibytes per second) instead of Kb/s (kilobytes per second). Additionally, the displayMode in Advanced Configuration has been updated to consistently reflect kibibytes. This change may affect any integrations such as rules that rely on the previous units. Review and update your configurations as needed to maintain compatibility.

### ITRS Analytics in the Gateway Setup Editor

Starting with version 7.2.x, the Gateway-obcervConnection and Obcerv-connection plugins have been deprecated and replaced by the Gateway-itrsAnalyticsConnection and itrs-analytics-connection plugins, respectively. All other references to Obcerv have been updated to ITRS Analytics using the GSE display name feature.

### Java version for Active Console and Web Server

Beginning 7.2.x, Active Console and Web Server (Web Dashboard) require Java 17 as the minimum supported version.

## Upgrade to Geneos 7.1.x

### Collection Agent and Collection Agent plugins required Java version

Beginning 7.1.x, the Collection Agent and Collection Agent plugins have been upgraded to version 5.0.0. Consequently, the minimum Java version requirement for both the Collection Agent and Collection Agent plugins version 5.0.0 is Java 21. This may require you to upgrade the Java versions on the machines where Collection Agent is running.

## Upgrade to Geneos 7.0.x

### Upgrade to Gateway 7.0.0 or later before enabling ITRS Analytics publishing

Gateway versions earlier than 7.0.0 are not supported and may encounter:

- Connection failures to the ITRS Analytics ingestion service
- Data publishing errors
- Incompatibility with gRPC/HTTP/2 protocols

If you are already using ITRS Analytics or plan to implement publishing, ensure your Gateway is updated to version 7.0.0 or higher.

### cURL library package

Beginning 7.0.x, the cURL library is now packaged in RHEL 8 and RHEL 9 builds of both Netprobe and Gateway. This does not change any existing behaviour, it is only an additional file in the package.

### Netprobe required Java version

Beginning 7.0.x, Netprobe requires Java 11 as the minimum supported Java version. This is necessary for the proper operation of Control-M, E4JMS, IBMi, JMX, Publisher, REST API, REST Extractor, and Uptrends plugins. However, Java 8 remains supported for Geneos versions 6.9.0 and earlier.

## Upgrade to Geneos 6.9.x

### Updated dimensions for OpenTelemetry plugin

The default OpenTelemetry attributes extracted by the OpenTelemetry plugin have been updated. This means that the dimensions and properties collected by default have changed. The plugin configuration can be modified to control which OpenTelemetry attributes are collected.

To ensure correct Geneos data mapping, it is recommended to review and adjust your plugin configuration and Gateway dynamic entity mapping configuration after upgrading.

### Netprobe package

Beginning with Geneos 6.9.0, the Netprobe package is available in both standard and minimal versions.

The standard package includes the Collection Agent plugins and all other plugins suitable for most cases. For example, `geneos-netprobe-standard-<version>-linux-x64.tar.gz`. The minimum package is smaller in size and excludes the Collection Agent and all of its plugins. For example, `geneos-netprobe-minimal-<version>-linux-x64.tar.gz`.

## Upgrade to Geneos 6.8.x

### Deploying Netprobe in Kubernetes

The default configuration for the Netprobe helm chart (`itrs/netprobe`) version 6.8.0 and newer has been changed to remove the use of host ports. This means that by default the plugins Statsd, Opentelemetry, Fluentd, and Prometheus will be run in the `StatefulSet` pod instead of the `DaemonSet` pod. Additional services will be created to route data to the  `StatefulSet` pod. This is to ensure the default Netprobe install meets the Kubernetes pod security standards for baseline and restricted modes. A new setting is added called `daemonSet.runAgentPluginsOnNode`, which, when set to true, will run the plugins on the DaemonSet pods, similar to the previous behavior. To fetch a list of all possible configuration options, run: `helm show values itrs/netprobe`.

### Network plugin

The following changes are applied to the Network plugin dataview column names. These changes provide consistent naming and meaning to the metrics. We recommend that you review and update any existing x-paths where these column names are used.

Note the the column names you see in the dataview may depend on the sampler configuration. For example, sampler settings `showMBits` and `showAbsolute`.

- `mbitSend` to `MbitSend`
- `kbyteSend` to `KiBSend`
- `mbitSendRate` to `MbitSendRate`
- `kbyteSendRate` to `KiBSendRate`
- `mbitReceive` to `MbitReceive`
- `kbyteReceive` to `KiBReceive`
- `mbitReceiveRate` to `MbitReceiveRate`
- `kbyteReceiveRate` to `KiBReceiveRate`

Columns names `packetSendDrop` and `packetReceiveDrop` are not available when `showAbsolute` is set to `false` (default). Instead `packetSendDropRate` and `packetReceiveDropRate` columns are added to be consistent with the rest of the rate-based metrics.

### Corvil Integration

Corvil Integration (geneos-cnpi) version 2.0.0 has been updated to work with Corvil XML API version 2. Ensure that the version of Corvil you are connecting to supports the version 2 API.

### Device IO plugin

In the Linux view of the Device IO plugin, the column `cpuUtiliisation` was corrected to `cpuUtilisation`. We recommend that you review and update any existing x-paths where this column name is used.

## Upgrade to Geneos 6.7.x

### Collection Agent and Collection Agent plugins required Java version

Beginning 6.7.x, the minimum Java version requirement for Collection Agent and Collection Agent plugins is now upgraded from Java 11 to Java 17. This may require you to upgrade the Java versions on the machines where Collection Agent is running. Please contact [ITRS Support](https://support.itrsgroup.com/hc/en-us/articles/115004001525-How-to-use-and-navigate-the-new-ITRS-Support-Portal-as-well-as-raise-tickets) if you have any concerns regarding this.

### Updated Prometheus AlertManager firing severities

The firing severities of Prometheus AlertManager have been updated to use the new signal severities introduced in CA datamodel version 4. Please update these to any of the following signal severities: `NONE`, `WARNING`, or `CRITICAL`. See [Prometheus and Alert Manager](https://docs.itrsgroup.com/docs/geneos/collection/prometheus/current/user-guide/prometheus/index.html) for more information.

Additionally, there are new options in `PrometheusTargetScrapeCollector`, but these are optional.

## Upgrade to Geneos 6.6.x

The following changes were implemented to the behaviour of the self-monitoring views created by Gateways and Netprobes. The changes include renaming of dataviews and the data displayed by default. This will affect any existing x-paths used to query these dataviews. These changes are necessary to improve performance, particularly when large number of entities are created and removed in dynamic environments.

### Gateway: Entities self-monitoring dataviews

By default, each Gateway automatically creates a self-monitoring Managed Entity called **<gateway_name> Info**. The behaviour of the **Entities** dataview in this Managed Entity has now changed.
  - **Entities** dataview is now called **Entities Summary**.
  - Previously this dataview displayed a detailed list of all entities, now, this dataview shows summary stats.
  - If you want the detailed list of all entities, you can create a sampler using **Gateway-managedEntitiesData** plugin and set the mode to show summary and details. This creates two dataviews: **Entities Summary** and **Entities Details**. This custom sampler can then be used to override the default behaviour by setting the Gateway sampler override configuration in the **Operating environment -> Self Monitoring** setup.

The default behaviour of the Gateway-managedEntitiesData plugin has now changed.
  - **Entities** dataview is now called **Entities Summary**.
  - Previously this dataview displayed a detailed list of all entities, now, this dataview shows summary stats.
  - If you want the detailed list of all entities, change the plugin configuration to set the mode to show summary and details. This creates two dataviews: **Entities Summary** and **Entities Details**.

### Netprobe: Dynamic Entities Health self-monitoring dataviews

By default, each Netprobe that is configured to process dynamic entities for data from a Collection Agent will automatically create a self-monitoring Managed Entity called **<probe_name> Netprobe Info**. The behaviour of the **Entities** and **Streams** dataview in this Managed Entity has now changed.
  - By default, the **Entities** dataview will now only list any dynamically created entities that are in error state instead of listing all entities.
  - By default, the **Streams** dataview will now only list any dynamically created streams that are in error state instead of listing all streams.
  - If you want the detailed list of all entities and streams, you can create a sampler using dynamic-entities-health plugin and set the option to show all entities and streams. This custom sampler can then be used to override the default behaviour by setting the Netprobe sampler override configuration in the **Operating environment -> Self Monitoring** setup.

The default behaviour of the dynamic-entities-health plugin has now changed.
  - By default, the **Entities** dataview will now only list any dynamically created entities that are in error state instead of listing all entities
  - By default the **Streams** dataview will now only list any dynamically created streams that are in error state instead of listing all streams
  - If you want the detailed list of all entities and streams, change the plugin configuration to show all entities and streams.

These updates will affect any x-paths that reference the affected dataviews. Please ensure the x-paths are updated to match the new dataviews.

## Upgrade to Geneos 6.5.x

### Netprobe and Collection Agent using Helm charts

Geneos 6.5.x now supports running a Netprobe image as a non-root user with privileged file access when the mode is `DaemonSet` and persistence is enabled. However, if you set the Netprobe image tag in the values file, the Helm chart will use the specified Netprobe image version.

When upgrading to this version, it is recommended to leave the Netprobe image tag setting blank in the values file, unless there is a need to use a specific version of Netprobe for troubleshooting purposes. If you use a Netprobe image that does not have privileged file access, user assignments and snoozes on dataviews from DaemonSet Netprobes will not be persisted when you reinstall the Helm chart.

The `Deployment` mode is no longer supported for Netprobe. To deploy a Netprobe in only one pod, you must set the `mode` to `StatefulSet`.

The following settings under the `persistence` section in the values file have been renamed:
- `directory` — Use `agentDirectory` setting instead to specify the directory where DaemonSet persistence files for Collection Agent are stored.
- `deploymentClaimSize` — Use `claimSize` setting instead to specify the size of the PersistentVolumeClaims used by StatefulSets.

The **deployment** section in the values file is no longer supported. Please use the **statefulSet** section instead. All the settings that were in the **deployment** section can be used in the **statefulSet** section and will be applied to the pods controlled by the StatefulSets.

## Upgrade to Geneos 6.4.x

### FKM samplers created under a Dynamic Entity

Beginning Geneos 6.4.0, the entity name of FKM samplers created under Dynamic Entity is no longer  in the `name` column of the dataview. The name is now displayed in the following format: `dim1.dim2. ... .dimN.eventName`, where:
- `dimX` are only the dimensions that are not mapped to `Entity` or `Ignore`.
- `eventName` is the name of the event corresponding to this stream.

The Managed Entity name is also removed from the `sourceAlias` field of outbound stream messages. The format of the `sourceAlias` field is the same as mentioned above.

## Upgrade to Geneos 6.3.x

### Netprobe and Collection Agent using Helm charts

This version now supports running a Collection Agent image as a non-root user with privileged file access when either log collection or persistence, or both are enabled. To support this, the Collection Agent image tag is now determined during the installation of the Helm chart, and the agent image tag setting in the values file is left blank by default. Setting the agent image tag in the values file will force the Helm chart to use the specified Collection image version.

When upgrading to this version, the agent image tag setting should be left blank in the values file, unless there is a need to use a specific version of the Collection Agent for troubleshooting purposes.

### Installing Gateway using Helm charts

Beginning Geneos 6.3.0, Gateway can now be installed in the cluster with a setup file. See [Installation with a setup file](https://docs.itrsgroup.com/docs/geneos/current/administration/orchestrated-environments/installation-using-helm/index.html#installation-with-a-setup-file) for more information.

## Upgrade to Geneos 6.2.x

### SQL toolkit plugin for MySQL and MariaDB

The SQL toolkit plugin 6.2.1 and newer has a timeout configuration to cancel the query after the timeout period has passed. As a result of this change, conncection to MySQL and MariaDB databases, configured with or without the new timeout setting, will require an additional connection to handle query cancellation. Please make sure this does not impact the overall maximum allowed client connections to your database.

### Installing Netprobe and Collection Agent using Helm charts


**Note**


If you had already configured a non-default persistence directory where Collection Agent DaemonSet persistence files are stored, then this issue can be ignored.



The default `persistence.directory` in Netprobe Helm chart version 6.2.1 and older:

  ```
  persistence:
      directory: /var/lib/geneos/collection-agent-{{ .Release.Name }}
  ```

The default `persistence.directory` in Netprobe Helm chart version 6.2.2 and newer

  ```
  persistence:
      directory: /var/lib/geneos/collection-agent-{{ .Release.Namespace }}-{{ .Release.Name }}
  ```

If you are using the default persistence directory, then upgrading to Netprobe Helm chart version 6.2.2 or newer means any existing persistence data will be lost, including pod logs that may be buffered in the pipeline store and the Kubernetes log collector position files. After upgrading, the log collector will tail existing log files instead of resuming from the last known position. However, if **logs.readFromBeginning** is `true`, then we recommend following the workaround below in order to preserve the persistence data and prevent existing pod logs from being reprocessed from the beginning.

As a workaround, you can either do one of the following:

- Configure the `persistence.directory` path to override the new default with the previous default.

    ```
    persistence:
        directory: /var/lib/geneos/collection-agent-{{ .Release.Name }}

    ```

  
**Note**


This workaround may result in a clash if two releases with the same name but different namespaces are installed.



- Scale down the DaemonSet by manually renaming the directory to the new default name on each of the affected nodes, and then upgrade your Helm chart to the new version.

### Active Console

Workspaces created in Active Console 6.2.0 and newer will have the **Follow selection** feature in State Tree enabled by default. This means the State Tree will automatically expand to select and identify items selected elsewhere in the Active Console. If you do not want this behavior, you can untick the **Enable follow selection** setting in **Tools > Settings > General > State Tree**.

A number of settings in the Active Console Settings dialog are now rearranged to make it easier to use. This change only affects the appearance and grouping of settings it does not change the behavior of Active Console when opening new or existing workspaces.

## Upgrade to Geneos 6.0.x

### Netprobe and Collection Agent

Upgrading to Netprobe 6.x requires you to also upgrade the Collection Agent and its plugins to version 3.x. The compatible versions of Collection Agent 3.x and its plugins are packaged with the Netprobe 6.x. The latest versions of Netprobe and Collection Agent are also compatible with updated Helm charts and Docker images.


**Note**


The configurations, metric names, and dimensions of Collection Agent and its plugins have all changed. These changes are not backward compatible. See [Upgrading to Collection Agent 3.x](https://docs.itrsgroup.com/docs/geneos/current/collection/collection-agent/upgrade-collection-agent/index.html) for more information.



- The following Netprobe plugins, which are already deprecated and not supported, are now removed from Netprobe. These plugins no longer work in Geneos 6.0 and newer. However, the plugins may still continue to work in Geneos 5.x, but they remain unsupported. Please contact [ITRS Support](mailto:support@itrsgroup.com) if you have any concerns.
  - Citrix Apps, Citrix Processes, Citrix Sessions, Citrix Summary
  - Combo
  - Component Versions
  - DQM Compare, DQM Updates
  - Effix Status
  - Fix Cameron Status
  - Gissing
  - RTIC Latency
  - SWX
  - Triarch Latency
  - UL Bridge

- The following Netprobe plugins are now deprecated in configuration and are no longer supported. However, the plugins may still continue to work in Geneos 5.x and 6.x, but they remain unsupported. Please contact [ITRS Support](mailto:support@itrsgroup.com) if you have any concerns.
  - GL Greffon, GL Lost Orders, GL Order Book, GL Permissions, GL SLC, GL SLC Relay, GL SLE, GL SLE TCP
  - MISS-X
  - PATS Status, PATS Trading Breaches, PATS Users
  - SETS SLC
  - SU
  - Tradeview

- Market Data Monitoring (MDM) plugin in Netprobe 6.0.x and newer does not require an application key file (`mdm_appkey.txt`) in the Netprobe directory to function. This additional requirement has been removed, but the plugin still requires a valid Licence Daemon token to function.
- The dataview generated by the Netprobe CPU plugin on the Windows platform is now more consistent with other Unix platforms. This means the value in the first column of the dataview listing the name of the logical CPU has changed to `cpu_<num>_logical#<num>`. This may break existing x-paths that reference the row name. Please check the Gateway configuration with reference to the CPU plugin dataview on the Windows platform.
- The Kubernetes specific Netprobe package (`geneos-netprobe-<version>-kubernetes.tar.gz`) is no longer available to download from the [ITRS Downloads](https://resources.itrsgroup.com/downloads) website. Both the Kubernetes plugin and the template Gateway configuration for Kubernetes are now available in the standard Netprobe and the Gateway packages, respectively.   We recommend that you set up Kubernetes monitoring using the Helm Charts available through ITRS Helm repository. See [Installation using Helm](https://docs.itrsgroup.com/docs/geneos/current/administration/orchestrated-environments/installation-using-helm/index.html) for more information.

### Gateway

Geneos 6.0 introduced capabilities to centrally manage the Collection Agent configuration (`collection-agent.yml`) in the Gateway through the Gateway Setup Editor. As part of this change, the Gateway Dynamic Entity configuration section has new settings to manage the Collection Agent. All changes in the Gateway configuration are backward compatible, meaning your current Gateway configuration remains valid when upgrading to Geneos 6.x. For more information, see [Collection Agent Setup](https://docs.itrsgroup.com/docs/geneos/current/collection/collection-agent/collection-agent-setup/index.html) and [Dynamic Entities](https://docs.itrsgroup.com/docs/geneos/current/processing/configuration/dynamic_entities/index.html).

Note: This feature requires Gateway and Netprobe version 6.x. It is also recommended you upgrade Active Console and Gateway Setup Editor to version 6.x.

- If you upgrade Gateway to 6.0 or newer, you must use Active Console 5.4.x or newer due to changes in the way Gateway provides database connection details to Active Console. Older Active Console might still function, but they won't have the Gateway database connection information needed to query historical data from databases.
- Gateway now adds a new self-monitoring entity named **<probe-name> Netprobe Info** for every Netprobe that is configured with Dynamic Entities. This is the default behaviour, but it can be disabled in the **Operating Environment** section of the Gateway configuration. This self-monitoring entity contains the Dynamic Entity Health views that are useful for understanding the data received from the Collection Agent and how that data is represented in Geneos.

## Upgrade to Geneos 5.14.x

### New binary file name for Netprobe package

As part of the improvements to our deployment process, the Netprobe package `geneos-netprobe-5.14.x-linux-x64.no_ca.tar.gz` has been renamed to `geneos-netprobe-minimal-5.14.x-linux-x64.tar.gz`.

### Run Collection Agent via Netprobe

Collection Agent and its plugins is no longer packaged with the Netprobe in Geneos 5.14.7 and the subsequent 5.x versions. If you want to run Collection Agent via Netprobe, please upgrade to the current 6.x version of Geneos.

### Geneos and Obcerv connectivity

Geneos 5.14.0 is the first fully supported release that is compatible with ITRS Obcerv 1.0. You might have deployed Geneos Gateway and Netprobe versions older than 5.14.0 to integrate with beta versions of Obcerv. There are several changes to both Netprobe and Gateway such as Publisher plugin settings and Obcerv connection settings, respectively. We recommend you upgrade to version 5.14.0 or newer to minimise any compatibility issues.

### Updated Refinitiv RTDS Integration

Geneos 5.14.0 includes an updated Refinitiv RTDS integration. This integration replaces the previous one from Geneos 4.9.0. It is recommended that Dynamic Entities using the old types are re-configured as there have been some structural changes and renaming as part of the rebranding exercise. For more information, see [Refinitiv RTDS](https://docs.itrsgroup.com/docs/geneos/current/collection/refinitiv-rtds/index.html).

## Upgrade to Geneos 5.12.x

### Apache Log4j library

The Apache Log4j library in the Active Console, Web Dashboard, Terracotta Messaging integration, and VMware Monitor integration, has been upgraded to 2.17.1 to fix the security vulnerability in Apache Log4j (CVE-2021-44832). We recommend upgrading to the latest version Geneos 5.12.0 or newer.

## Upgrade to Geneos 5.11.x

### Apache Log4j library

Upgraded the Apache Log4j library to fix the following vulnerabilities:

 * The Apache Log4j library in the Active Console, Web Dashboard, Terracotta Messaging integration, and  VMware Monitor integration, has been upgraded to 2.17.0 to fix the security vulnerability in Apache Log4j (CVE-2021-45105). We recommend upgrading to the latest version Geneos 5.11.3 or newer.
 * The Apache Log4j library in the Active Console, Web Dashboard, Terracotta Messaging integration, and VMware Monitor integration, has been upgraded to 2.16.0 to fix the security vulnerability in Apache Log4j (CVE-2021-45046). We recommend upgrading to the latest version Geneos 5.11.2 or newer.
 * The Apache Log4j library in the Active Console, Web Dashboard, Terracotta Messaging integration, and VMware Monitor integration, has been upgraded to 2.15.0 to fix the security vulnerability in Apache Log4j (CVE-2021-44228). We recommend upgrading to the latest version Geneos 5.11.1 or newer.

### Dynamic Entity mapping

Netprobe 5.11.0 introduced changes to the Dynamic Entities wherein additional checks are now made to ensure new metric data points being added to an existing entity have a consistent set of dimensions and attributes. As a result of this change, your current Dynamic Entity mapping configuration may reject metric data points that were previously accepted.

You will see the rejected metric in the Dynamic Entity plugin dataview with the reason `Entity Dimension clash`. Make sure that all metric data points mapped to a single entity have the same set of dimensions and attributes.

Further, Netprobe 5.11.0 removed the old **Dynamic entities > Mappings** configuration that was first introduced in Geneos 5.1.0. This configuration has already been deprecated and was replaced by more simplified **Dynamic entities > Mapping** configuration in Geneos 5.7.0.

### Publisher plugin

Publisher plugin has been updated so that **Success**, **Failed**, and **Lost** columns no longer just accumulate the number of events. Instead, the columns now show the number of occurrence of each event for each sample interval. We recommend that you review the existing rules that you have set in the Publisher plugin configuration.

## Upgrade to Geneos 5.9.x

### Netprobe package files per platform

Beginning Geneos 5.9.1, the `libssl.so.1.1` and `libcrypto.so.1.1` libraries are renamed to `libsslgeneos.so.1.1` and `libcryptogeneos.so.1.1` respectively for generic Linux and Linux on IBM POWER8 platforms to eliminate the dependency of libcurl to these libraries, and to reduce compatibility issues such as the following scenarios:

- When the Netprobe is run under elevated privileges in Linux, the runtime loader of Linux (`ld.so`) ignores the `RPATH` and `LD_LIBRARY_PATH`, so the Netprobe is unable to load the libraries from `<netprobe directory>/lib64`. For the libraries to be loaded, the path to `<netprobe directory>/lib64` has to be added to the trusted paths of `ld.so`. This can cause compatibility issues for other applications that run on the same machine. For more information, see [Run Netprobe under elevated privileges in Linux](https://docs.itrsgroup.com/docs/geneos/current/collection/netprobe/installation/quickstart-linux-and-other-platforms/index.html#run-netprobe-under-elevated-privileges-in-linux).
- When `/usr/lib64` or any library folder that has OpenSSL libraries is loaded before the `netprobe conf`, files are loaded alphabetically in `/etc/ld.so.conf.d/*`. These libraries are not packaged with Netprobe but are in the `/usr/lib64` directory. Therefore, they might not be compatible.

### Geneos components

The additional HTTP security headers are now applied to all web responses sent on the Geneos communication ports (EMF2 ports):

- `X-Frame-Options: sameorigin`
- `X-XSS-Protection: 1; mode=block`
- `X-Content-Type-Options: nosniff`
- `Strict-Transport-Security: max-age=31536000; includeSubDomains`

This applies to all Geneos components including debug and ORB pages generated by Netprobes and Gateways.

### Licence Daemon

Beginning Geneos 5.9.x, the Licence Daemon detailed report is not available by default. A new [command line option](https://docs.itrsgroup.com/docs/geneos/current/administration/licence-daemon/index.html#command-line-options) `-report detail` is required to enable a detailed report.

### Gateway and Licence Daemon

Both Gateway and Licence Daemon are not compatible with RHEL 6.x (kernel 2.6.32). Both components now require at least RHEL 7.x or higher.

## Upgrade to Geneos 5.8.x

### Web Dashboard

Geneos 5.8.2 introduced changes to the `security.xml` file in the Web Server `config` folder as a result of the upgraded Spring Security libraries.

When upgrading to Geneos 5.8.2 or newer, we recommend that you use this latest version of `security.xml` and ensure that any previous `security.xml` files are removed from your local machine. Otherwise, the Web Server will not run properly.

### Express Report

Beginning Geneos 5.8.x, the Express Reports feature of Gateway is no longer available.

This feature will continue to be available and supported for Geneos 5.7.x and older until its end of life (EOL) date on 31 December 2021.

## Upgrade to Geneos 5.7.x

### Publisher plugin

The Publisher plugin Elasticsearch configuration schema has been refactored to support additional publishing destinations.

The plugin configuration prior to version 5.7.1 is not compatible with versions 5.7.1 and higher. We recommend that you update the configuration after upgrading to Geneos 5.7.1 and higher.

### Hardware plugin

The following metrics in the Hardware plugin have been changed:

- `ntpAvailability` is now `timeSyncSource`.
- `ntpLocalClockOffset` is now `timeSyncOffset`.

For more information, see [Hardware documentation](https://docs.itrsgroup.com/docs/geneos/current/collection/hardware/index.html).

### IBM i plugin

Beginning Geneos 5.7.x, the `severityCodeFilter` metric and **filters > queueNameFilter** configuration in the IBM i Queue plugin have been deprecated.

The new filters for **[Queue library](https://docs.itrsgroup.com/docs/geneos/current/collection/ibmi/index.html#Advanced_configuration_..820)** and **[Queue name](https://docs.itrsgroup.com/docs/geneos/current/collection/ibmi/index.html#Advanced_configuration_..820)** replaces the **filters > queueNameFilter**.

### Web Dashboard

Web Dashboard requires the `fontconfig` package to be installed in the system to start up. Beginning Geneos 5.7.x, Web Dashboard now uses Open Sans as its default font when a required font is not available in the system.

For more information, see [Fontconfig dependency in Web Dashboard documentation.](https://docs.itrsgroup.com/docs/geneos/current/visualization/web-dashboard/index.html#install-web-dashboard)

### Dynamic Entities

The new and simplified mapping configuration replaces the Dynamic Mapping Configuration. Any existing configurations using the previous setup will continue to work. However, we recommend you migrate to the new [Dynamic Entities > Mapping](https://docs.itrsgroup.com/docs/geneos/current/processing/configuration/dynamic_entities/index.html):

- **Dynamic entities > Mapping type > Entity timeout** — the new default entity time out value is increased from `2 minutes` to `1 hour`.
- **Dynamic entities > Mapping type > Stale data timeout** — this is a new setting in this release to mark individual dataviews as containing stale data if the data has not been updated within the set timeout. The default is `2 minutes`.

### Gateway publishing to Gateway Hub

Beginning Geneos 5.7, Gateway supports publishing data to Gateway Hub without schema. This schema-less publishing of data from Gateways is supported beginning Gateway Hub 2.4.x.

If you upgrade your Gateway to version 5.7.x or higher and you have many dataviews in the Gateway without a valid schema, then it is recommended that you also upgrade Gateway Hub to version 2.4.x or higher to take advantage of the automatic inference of schema in the Gateway Hub. Gateway Hub 2.3.x and older will continue to report ingestion errors if a dataview is published without a schema.

## Upgrade to Geneos 5.6.x

### New binary file name for Geneos third-party plugins

The binary file naming convention in [ITRS Downloads](https://resources.itrsgroup.com/downloads) has been changed from `<plugin><version>.tar.gz` to `<plugin>-<version>.tar.gz`. This change applies to all Geneos versions.

### New ITRS Maven repository

 The  Maven repository has changed its location from `<url>https://itrsgroup.bintray.com/collection</url>` to `<url>https://maven.itrsgroup.com/repository/public</url>`. Please update all the existing links as they will stop working by end of February 2021.

### New workspace directory in Active Console

 Beginning  5.6.x,  now sets the new workspace default directory to the following paths:
 
 - On : `~\ITRS\ActiveConsole`
 - On  and : `~/ITRS/ActiveConsole/`
 
 The new default workspace directory is used when creating a new workspace, but all existing workspaces are not affected. For more information, see [Workspace directory in Active Console](https://docs.itrsgroup.com/docs/geneos/current/visualization/active-console/configuration/workspace-selection/index.html#workspace-directory).

## Upgrade to Geneos 5.5.x

### New binary file name for Geneos components

 As part of the improvements to automate our deployment process, the binary file naming convention in [ITRS Downloads](https://resources.itrsgroup.com/downloads) has been changed from `geneos-<component>-<version>.<os>.tar.gz` to `geneos-<component>-<version>-<os>.tar.gz`. This change applies beginning  5.5.x.

## Upgrade to Geneos 5.4.x

### Self-monitoring in Geneos

 Beginning  5.4.x, self-monitoring in  is now enabled by default with no configuration required.
 
 This results in an **Entity** being dynamically created called `<gateway_name> Info` which contains samplers and dataviews that are automatically enabled with no configuration required. These samplers and dataviews are created using the existing  plugins which you may already have manually configured in your . 
 
 If you do not wish the  to automatically create a self-monitoring **Entity**, you can disable this feature in the  **> Operating environment** section.
 
 For more information, see [operatingEnvironment > selfMonitoring in  Operating Environment](https://docs.itrsgroup.com/docs/geneos/current/processing/configuration/gateway_operating_environment/index.html#operatingenvironment--selfmonitoring) documentation.

### E4JMS plugin

 Beginning  5.4.x, the E4JMS plugin supports SSL client authentication. This feature introduces breaking changes to the E4JMS plugin SSL implementation for older  versions.
 
 If you are using SSL connections on your E4JMS plugins, you must update your configuration when using the new schema.
 
 For more information, see [E4JMS Plugin Technical Reference](https://docs.itrsgroup.com/docs/geneos/7.2.0/collection/e4jms/index.html).

### File Keyword Monitor plugin

 Beginning  5.4.x, the  plugin uses Perl Compatible Regular Expressions (PCRE) by default. Be aware that this may introduce breaking changes in your implementation.
 
 For more information, see the following documentation in the :
 
 - [Regular expressions](https://docs.itrsgroup.com/docs/geneos/current/collection/fkm-config/index.html#regular-expressions)
 - [Notable differences between POSIX and PCRE](https://docs.itrsgroup.com/docs/geneos/current/collection/fkm-config/index.html#character-classes)

## Upgrade to Geneos 5.2.x

### State Tracker plugin

 The  **Rewind** option in  is now disabled by default.
 
 For more information, see [trackerGroup > trackers > tracker > rewind in  Technical Reference](https://docs.itrsgroup.com/docs/geneos/current/collection/state-tracker-config/index.html#trackergroup--trackers--tracker--rewind).
 If you enable this option, this may cause a sudden increase in your CPU usage with no known changes in the monitored file. Since the State Tracker will track the monitored file from the beginning, and not when the file grows for new events.

### Dynamic Entities

 and  have each been updated to support licensing of  plugins. All three of these components must be updated to  5.2.x or higher for the  feature to be supported in .
 
 plugins require an additional licence to use. Please contact your  Account Manager or [Sales](mailto:sales@itrsgroup.com).

### Gateway and Licence Daemon

 If you are upgrading to  5.2.x or higher, you must also upgrade  to version 5.2.x or higher.

### StatsD Plugin

 The  configuration in the packaged  (`collection-agent.yml`) now uses the default protocol `UDP` and `port 8125`. Previously, this was set to protocol `TCP` and `port 7780`.

## Upgrade to Geneos 5.0.x

 #### Important
 
 * The  Maven repository has changed its location from `<url>https://itrsgroup.bintray.com/collection</url>` to `<url>https://maven.itrsgroup.com/repository/public</url>`. Please update all the existing links as they will stop working by end of February 2021.
 * 5.1.x is not generally available to download except for  5.1.0 -64 package certified for deployment on Solace devices. Please download version 5.2.x or newer for all other deployments.
 * Support for  3.x ended on 30 April 2020. We strongly advise you to upgrade to version 4.x or newer as soon as possible.
 * From the release of  5.0.x, there will be no interoperability with other  components older than version 3.6.x. In order to successfully deploy or upgrade to  5.0.x in a staged manner, you must first ensure that no other connecting  components are older than version 3.6.x. This change is a result of the removal of LZO compression support in the inter-component EMF2 communication protocol.
 * plugins require an additional licence to use. Please contact your  Account Manager or [Sales](mailto:sales@itrsgroup.com).
 
 If you have any question or concerns, please contact [ITRS Support](mailto:support@itrsgroup.com).

### Netprobe

The Hardware plugin now uses a new method of obtaining `memoryAvailable` and `memoryAvailablePct` for Linux platforms. The metrics are now based on the same calculation Linux uses to calculate the `memAvailable` field in `/proc/meminfo`. For more information, see the [Hardware Plugin](https://docs.itrsgroup.com/docs/geneos/current/collection/hardware/index.html) documentation.

Ensure that any affected Gateway rules and thresholds are reviewed.

### Gateway

Gateway 5.0 cannot publish data to Gateway Hub 1.4 or older versions. This is due to the changes in the publishing format in order to improve performance.

Gateway Setup Editor now enables the Simplified Comments by default. With `simplifiedComments` enabled, GSE removes all icons that indicate comments. You can only add, edit, or remove comments on named components in the Navigation panel.

The API for centralised configuration has changed since Early Access. Upgrade to Gateway 5.0 to use the centralised configuration with Gateway Hub 1.6 and above.

### Active Console

Active Console 5.0 now supports a new light theme user interface. The **Look and Feel** in the Advanced settings has been removed.

### Platforms and settings changes

Beginning with version 5.0, these Gateway settings are deprecated:

- **Managed Entity > Banner** (Advanced tab)
- **Sampler > Publish** (Visibility tab)

Changes to default Gateway configuration in version 5.0:

- **DatabaseLogging > logNetprobeSampleTimeForDataItems** default is now True.
- **Actions > action > sharedLibrary > runThreaded** default is now True.
- **Effects > effect > sharedLibrary > runThreaded** default is now True.

## Upgrade to Geneos 4.x.x


**Caution**


End of life for 4.x.x is 31 May 2023. If you are using 4.x.x, we advise you to upgrade to 5.x.x or newer.



### Upgrade to Geneos 4.11.x

In the Gateway, the behaviour of the `_COMMENT` environment variable has changed for actions fired by the unassignment of a data item. Previously, the comment provided when the item was assigned was placed in the `_COMMENT` environment variable for both assignment and unassignment events. It is now possible to configure Gateways to require comments for both assignment and unassignment events. This means for actions fired by unassignment events, the comment provided when the item is unassigned is placed in the `_COMMENT` environment variable. The comment that was provided when the item was originally assigned is now moved to a new environment variable called `_PREVIOUS_COMMENT`.

Improved the Context Sensitive Help (CSH) for Gateway Setup Editor (Gateway Setup Editor) that is based on the specific content available online. Context sensitive help will launch your default browser to access the content online. To know more about this, see Host the documentation locally to use [GSE context-sensitive help in Gateway Setup Editor](https://docs.itrsgroup.com/docs/geneos/current/processing/configuration/gse_user_guide/#host-the-documentation-locally-to-use-gse-context-sensitive-help).

### Upgrade to Geneos 4.7.x

Geneos 4.7.x release introduces changes to the way arguments are parsed to **Commands, Actions, and Effects**.

These changes were required to provide consistent behaviour and understanding across both Netprobe and Gateway to simplify user experience.

We strongly recommend you check the configuration and behaviour of any **Commands, Actions, and Effects** before deploying to production.

For more information, see [Commands, Actions and Effects](https://docs.itrsgroup.com/docs/geneos/current/processing/monitoring-and-alerts/geneos_commands_tr/index.html).

### Upgrade to Geneos 4.0.x

The following changes are introduced to Geneos 4.0.x packages:

- Name of the package file is `geneos-<component>-<version>.<platform>.<tar.gz/zip>`.
  - For example, `geneos-netprobe-4.0.0.solaris-x64.tar.gz`.
- Packages contains a root directory <component>.
- Libraries are located within a sub-directory named `lib` or `lib64`:

![image](https://docscdn.itrsgroup.com/all/images/ga4-3-x-notice.png)


