Date: February 2025
Ironstream Hub – New Release Available
We are very pleased to announce that Ironstream Hub v1.3.11 is now generally available. This updated component release provides these new features:
Datadog metric and log target enhancements
Datadog requires the use of a specific naming and tagging convention for fields. Ironstream now conforms to that convention for a wide variety of IBM i data and for an initial selection of z/OS data.
For IBM i users renaming and tagging of data is provided for:
- over 40 journal entry types from the QAUDJRN security journal
- over 3,500 metrics from more than 60 standard Collection Services files
- the full set of data available in journals created by Precisely's MIMIX HealthLink feature
For z/OS users this release has renaming and mapping implemented for:
- SYSTEMSTATE data
- SMF type 30 (jobs)
- SMF type 110 subtype 1 class 3 (CICS transactions)
- SMF type 115 (MQ)
- SMF type 116 (MQ Accounting)
SMF data is complex, often having multiple repeating sections of data. The native implementation of this from the Ironstream z/OS collector is to 'flatten' the data by adding numeric suffixes to field names. For the Datadog metric endpoint, grouping of the metrics of the supported data types, listed above, into their relevant data sections is now performed automatically. Where this is done the numeric suffixes of field names are removed, making them easier to handle in dashboards and queries. Users can add the names of keys in a Datadog target, which will be converted to Datadog tags to further group data as they wish.
The range of data covered by this feature will continue to evolve in future releases.
You are encouraged to visit the Ironstream section of Precisely Ideas if you have specific requirements not covered here.
Important Note: If a user has any pipelines containing a Datadog target these must be removed before upgrading to this version of the Hub, then re-added. Failure to do so will result in the Hub Portal not being able to initialize.
A way to do this is as follows:
- add a different type of target (e.g. File) to the pipeline
- delete the Datadog target and save it
- upgrade the Hub
- when done, re-add the Datadog target to the pipeline
- remove the additional target
- save and restart the pipeline
A new BigPanda target
Ironstream has supported sending data to BigPanda for several releases by using a discrete Payload Wrapper process feeding an HTTP[S] target. The Ironstream Hub UI now allows you to more easily create a pipeline to send data to BigPanda with a specific target of that type that prompts for all necessary information including APP and API keys. The separate Payload Wrapper process is no longer needed as it is built into the new BigPanda target.
Settings page updates
A new Settings page was implemented in v1.3.10 with the ability to generate and download diagnostics. v1.3.11 extends the functionality to allow access and alteration of advanced Hub settings through the UI, as well as the ability to restart the Hub, Portal and IBM i configuration services. If advanced settings are changed and saved, then the user is prompted to restart services or may choose to do so at a later time.
Note: If the Hub is running as a zCX container under Docker, there are no 'services' and the three Hub containers will need to be manually restarted using native 'docker container' commands.
Information about all features plus fixed defects can be found in the Ironstream Hub Release Notes.
Contact Information
If you need technical assistance with any aspect of Ironstream please contact the Precisely 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 Account Executive or to: