April 2026
Ironstream Hub – New Release Available
We are very pleased to announce that Ironstream Hub v1.4.3 is now generally available. This updated component release provides these new features:
Security: Minimum TLS 1.2 enforced for all connections: The Hub now rejects any TLS connection below version 1.2 across all IBM i sources, IBM z/OS sources, TLS-enabled targets, and the IBM z/OS Discovery agent. Connections using TLS 1.0 or 1.1 will be refused. Review your environment for legacy TLS configurations before upgrading.
IBM i source management - centralized view: Multiple IBM i sources in a pipeline can now be managed from a single Manage Sources view. Add, view, and delete sources without navigating between pipeline configurations. A source drop-down lets operators switch between sources without leaving the pipeline view.
IBM i source import and export via CSV: IBM i source definitions can now be exported to CSV for review, version control, or bulk validation, and imported to create or update multiple sources in a single operation. Reduces manual entry for environments with large numbers of IBM i sources.
IBM i source groups and tagging: IBM i sources can now be grouped using Tag and Value pairs assigned in the source configuration, accessible via a new Source Tags tab. Supports operational grouping by region, environment, workload type, or any criteria your team uses.
Track IBM i profile distribution status and errors: IBM i profile distributions can now be monitored from a dedicated Distribution Results page. A single view covers all distributions across your IBM i environment, with per-distribution status and detailed error messages to reduce time spent diagnosing failures.
Support for Elastic Agent target: The Hub now supports sending log data to Elasticsearch via the Elastic Agent, covering IBM i and IBM Z data sources. Elastic Agent must be deployed and network-accessible from the Hub host before enabling this target. Licensing: Elastic Agent target availability depends on your source selection and licensing agreement. Contact your account team to confirm entitlement before enabling this feature.
Improved Datadog metrics identification with "ironstream" prefix: The Hub now prefixes all Datadog metrics with "ironstream_" to improve metric identification in monitoring dashboards. Metrics now appear as ironstream_ibm_i_* or ironstream_ibm_z_*. Note: This change will impact existing Datadog dashboards. If dashboards are not updated to include the new prefix, data will not be displayed.
ISO 8601 timestamp format for Datadog log targets: Ironstream now ensures that timestamps sent to the Datadog Log target conform to ISO 8601 format. This eliminates the need to create a Datadog log ingestion pipeline to reformat timestamps. Note: After upgrading to v1.4.3, existing pipelines that send data to Datadog targets must be recreated.
Concurrency factor for targets: Targets now support a configurable concurrency factor that controls how many parallel connections the Hub uses when sending data. Increase the concurrency factor to improve throughput to high-volume targets. Recommended starting point and ceiling values vary by target type.
Bug Fixes
Dynatrace log formatting: Logs sent to Dynatrace were malformed and could not be parsed. Logs are now generated as flat JSON records with ISO 8601 timestamps and required Dynatrace metadata fields.
Full information can be found in Ironstream documentation on the Precisely Help Center.
Contact Information
If you need technical assistance with any aspect of Ironstream please contact Precisely's Global Support team using the appropriate portal:
Customers - https://customer.precisely.com/
Partners - https://partner.precisely.com/
Other questions relating to this announcement should be directed to your Precisely Account Executive or to:
Product Manager bowen.yang@precisely.com
Product Owner arosha.tomaselli@precisely.com
------------------------------
Product Communications
*Precisely Software Inc.
Pearl River NY
------------------------------