ITRS Analytics version changes
Find version-specific updates for Geneos, including new features, resolved issues, and essential upgrade information.
Note
Use Version changes (Beta) to view release updates from the earliest supported IAX 2.x.x version to the latest version. Select the versions below to instantly see their release details.
Starting version: [Dropdown] To version: [Dropdown]
ITRS Analytics versions 2.17.11 to 2.18.0+p2.18.3 Copied
Summary: From version 2.17.11 to 2.18.0+p2.18.3
This summary highlights the changes from 2.17.11 up to 2.18.0+p2.18.3, giving you a quick overview of what has been added, changed, or removed in the range. For more information, refer to the product’s release notes.
| Platform known issues | Compatibility matrix | Security updates |
|---|
Upgrades and breaking changes Copied
Required releases and upgrade paths Copied
Certain releases of ITRS Analytics are designated as required or mandatory. You must upgrade to these versions to maintain support, security, and compatibility.
Warning
Failure to apply these releases may lead to unsupported configurations or compatibility issues with subsequent ITRS Analytics versions.
Required releases typically include:
- Critical patches addressing security vulnerabilities.
- Updates needed for future releases or features.
- Fixes for deprecated or unsupported functionality in earlier versions.
Required releases Copied
The following releases are mandatory for all users:
- ITRS Analytics 2.18.0+p2.18.3
- ITRS Analytics 2.17.6
- ITRS Analytics 2.17.4
- ITRS Analytics 2.15.5
- ITRS Analytics 2.12.0+1
- ITRS Analytics 2.9.1+3
- ITRS Analytics 2.8.0+4
For a complete overview of all releases, see the latest ITRS Analytics Release Notes.
Supported upgrade paths Copied
| Upgrade scenario | Recommended path | Notes |
|---|---|---|
| Users on the version immediately preceding a required release | Upgrade directly to the required release | Example: 2.15.x > 2.15.5 |
| Users on older versions that skip one or more required releases | Upgrade sequentially through each required release | Example: 2.10.1+2 > 2.12.0+1 (Required) > 2.15.x |
| Users skipping required releases entirely | Unsupported | May result in database, compatibility, or security issues |
| Planning upgrades | Always review release notes and test in staging | Check for pre-upgrade actions, dependencies, or configuration changes |
General upgrade instructions (all versions) Copied
Regardless of the version, upgrading ITRS Analytics from a lower version may reset some configurations. It is strongly recommended that you follow these steps during the upgrade process.
Verify and adjust hostnames Copied
If you configured a custom hostname in your existing installation, make sure to manually verify and update the hostname setting after the upgrade. It may not persist automatically.
Reinstall optional apps Copied
Optional apps are not retained automatically through the upgrade. Re-select and reinstall any apps you had previously chosen to ensure feature parity post-upgrade.
Downgrading to earlier versions Copied
Downgrading to an earlier version is not supported. Please ensure you back up all configurations and data before upgrading.
Version-specific considerations Copied
-
Upgrading to version 2.18.0
-
Version 2.18.0 introduces the ClickHouse migration for core platform workloads and requires additional preparation before upgrade, including capacity checks, configuration review, infrastructure transition planning, and post-upgrade validation.
-
Before upgrading, review Upgrade to version 2.18.0: ClickHouse migration guide, especially the guidance on choosing an infrastructure transition strategy for ClickHouse workloads.
-
-
Upgrading to version 2.17.11
- Manual selection required for Agentic AI (Beta) app in the KOTS Admin Console
- If you want to use the ITRS Agentic AI (Beta) app, you must manually enable it in the KOTS Admin Console configuration before upgrading.
- If you want to continue using any previously deployed Beta apps, you must manually enable them again in the configuration before upgrading.
- Manual selection required for Agentic AI (Beta) app in the KOTS Admin Console
Installation Package Copied
Installation Package 2.18.0+p2.18.3 Copied
Stable and RequiredThis ITRS Analytics package includes Platform 2.18.3.
Required release
ITRS Analytics 2.18.0+p2.18.3 is a required release.
When you upgrade an existing deployment with retained data, ITRS Analytics migrates that data from TimescaleDB to ClickHouse. This migration requires platform, application, and infrastructure changes that must be completed outside the installation process. These temporary infrastructure changes do not apply to a straightforward fresh installation because there is no TimescaleDB-to-ClickHouse data migration to run. While migration is ongoing, there can be gaps in the historical data returned by queries because only the data that has already been migrated to ClickHouse is available. This is expected during the upgrade. All historical data becomes available after the migration completes. For important upgrade guidance, see Upgrade to version 2.18.0: ClickHouse migration guide.
If you are installing on Embedded Cluster, or if your BYO cluster uses a storage driver that creates persistent volumes with node-level affinity, you must disable the ClickHouse node selectors in the KOTS Admin Console under Advanced Settings > Enforce ClickHouse Node Selector. See Review storage driver node affinity.
- REP-3090 - Added Storage Class and disk configuration options for ClickHouse in KOTS, simplifying storage setup for KOTS-based deployments.
- REP-3143 - Enabled ephemeral storage for all ITRS Analytics app charts on Embedded Cluster (EC) KOTS deployments. All EC installations (online and airgapped) now set
useEphemeralStorageto true by default during installation, enabling high availability (HA) support.
Bill-of-materials and Docker images Copied
You can download the ITRS Analytics 2.18.0+p2.18.3 YAML file to access details such as components, product description, version URL, subsystems, version tags, and other relevant information.
Installation Package 2.17.12 Copied
StableThis ITRS Analytics package includes Platform 2.17.7.
- REP-3273 - Added the Enforce Zone Spread setting in the KOTS Admin Console to control even replica distribution across availability zones in multi-zone clusters. A preflight check validates compatibility with the cluster’s zone topology before installation or upgrade, helping prevent scheduling issues in multi-zone environments.
- REP-3354 - Updated ITRS Analytics Platform to version 2.17.7. Please check the Platform release notes to view other detailed changes.
Bill-of-materials and Docker images Copied
You can download the ITRS Analytics 2.17.12 YAML file to access details such as components, product description, version URL, subsystems, version tags, and other relevant information.
Installation Package 2.17.11 Copied
This ITRS Analytics package includes Platform 2.17.6.
-
REP-3308 - ITRS Analytics Agentic AI Beta app version 0.2.0 is now available. For more information, see the Agentic AI app 0.2.0 release notes. If you are installing ITRS Analytics 2.17.11 with the Agentic AI Beta app in an air-gapped environment, see this FAQ for the known issue and workaround.
-
REP-3313 - Updated ITRS Analytics Query Service app to version 2.22.5.
Bill-of-materials and Docker images Copied
You can download the ITRS Analytics 2.17.11 YAML file to access details such as components, product description, version URL, subsystems, version tags, and other relevant information.
ITRS Analytics Platform Copied
Platform 2.18.3 Copied
This platform is packaged with ITRS Analytics 2.18.0+p2.18.3.
- HP-631 - Added a new Logs Query Service and API backed by ClickHouse to improve log query capabilities.
- HP-2132 - Added support for informational attributes in the data model so these values can be stored for context without affecting lookups.
- HP-2746 - Added entity filtering by metric or log-name existence so queries can target only entities that contain the required datapoints.
- HP-2772 - Consolidated platform gRPC services into a single port with a larger shared thread pool to improve scalability and simplify service connectivity.
Platform 2.17.7 Copied
This platform is packaged with ITRS Analytics 2.17.12.
- REP-3273 - Added the Enforce Zone Spread setting in the KOTS Admin Console to control even replica distribution across availability zones in multi-zone clusters. A preflight check validates compatibility with the cluster’s zone topology before installation or upgrade, helping prevent scheduling issues in multi-zone environments.
- REP-3354 - Updated ITRS Analytics Platform to version 2.17.7. Please check the Platform release notes to view other detailed changes.
Platform 2.17.6 Copied
This platform is packaged with ITRS Analytics 2.17.11.
- HP-3045 - Upgraded the OpenTelemetry Java agent to the latest 2.x release to improve tracing reliability and align with current upstream capabilities.
- HP-3626 - Improved the performance of PostgreSQL-backed entity subscription queries through query-path optimizations, including cache and index enhancements.
- HP-3656 - Added a new configuration parameter,
inactivityThresholdTimeSlots, to the Intermediate Entity Stream (IES). This controls how many consecutive 15-minute time slots of inactivity must pass before an entity is marked as inactive.- Default:
2(maintains existing behavior — 30-minute inactivity window) - Valid range:
2–20(30 minutes to 5 hours)
This is an advanced setting. Please do not modify it unless advised by ITRS Support.
- Default:
ITRS Analytics Apps Copied
Agentic AI Copied
0.4.0 (Beta) Copied
- IAA-144 - Updated Python 3.11 in the documentation indexing image to address vulnerability CVE-2026-3298.
- IAA-146 - Updated
lxmlin the documentation indexing image to address vulnerability CVE-2026-41066.
0.3.0 (Beta) - Packaged with ITRS Analytics 2.18.0+p2.18.3 Copied
For more information, refer to the Agentic AI app release notes.
0.2.0 (Beta) - Packaged with ITRS Analytics 2.17.11 Copied
For more information, refer to the Agentic AI app release notes.
Alerting Copied
2.11.0 - Packaged with ITRS Analytics 2.18.0+p2.18.3 Copied
- HASA-768 - Updated the context selector to align with the new Entity Viewer context model.
- HASA-769 - Removed the severity counts from the grouped entity listing.
- HASA-770 - Upgraded the app dependencies to support ITRS Analytics Platform version 2.18.0.
API Gateway Copied
2.9.0 - Packaged with ITRS Analytics 2.18.0+p2.18.3 Copied
- HAPA-263 - Rate limiting now applies to all public REST endpoints, with HTTP 429 returned when limits are exceeded.
- HAPA-294 - Upgraded the app dependencies to support ITRS Analytics Platform version 2.18.0.
Capacity Copied
1.5.0 - Packaged with ITRS Analytics 2.18.0+p2.18.3 Copied
- IAS-257 - Upgraded app dependencies to support ITRS Analytics Platform 2.18.0.
- IAS-412 - Enabled useEphemeralStorage: true to use ephemeral storage for PVCs created by the app. This ensures that the app can be rescheduled in an embedded cluster in the event of a node failure.
Capacity Planner Copied
2.6.0 - Packaged with ITRS Analytics 2.18.0+p2.18.3 Copied
- CPPUB-221 - Updated the Kubernetes label app.kubernetes.io/part-of from obcerv to iax across all Capacity Planner workloads.
Logs Copied
For more information, refer to the Logs app release notes.
Query Service Copied
2.22.5 - Packaged with ITRS Analytics 2.17.11 Copied
- ESCA-1678 - Fixed an issue where an excessive number of Java Timer classes were created when subscribing to Dashboard severity state. This has been updated to use a fixed thread pool, reducing resource usage and preventing potential slowdowns in the Dashboard backend over time.
Disclaimer
The information contained in this document is for general information and guidance on our products, services, and other matters. It is only for information purposes and is not intended as advice which should be relied upon. We try to ensure that the content of this document is accurate and up-to-date, but this cannot be guaranteed. Changes may be made to our products, services, and other matters which are not noted or recorded herein. All liability for loss and damage arising from reliance on this document is excluded (except where death or personal injury arises from our negligence or loss or damage arises from any fraud on our part).