Ironstream data flows from an agent, through Hub, to an external target.
There are two flavors of Ironstream agent:
- Ironstream Agent for IBM Z (z/OS)
- Ironstream Agent for IBM i
An Ironstream Agent will need to be installed on each LPAR that you want to monitor.
Hub:
- Runs as a service on a Windows or Linux system.
- Can receive information from multiple agents.
- Includes a Configuration Tool for configuring the IBM i sources from which it will receive messages.
Events and performance data that are forwarded from agents to Hub can be sent to the targets that follow:
-
File – this can be monitored by third party tools like a Splunk forwarder or a Logstash.Note: When writing to file, all necessary precautions to ensure that this data is protected should be taken. This includes ensuring that access control is applied to the machine hosting to the file.
- HTTP[S] - data can be sent to an HTTP or HTTPS end point
-
Splunk via TCP – IBM Z sources only.