|
Term |
Short Version |
Definition |
|---|---|---|
| Ironstream Hub | Hub | Software for creating an environment which transfers data from the Ironstream agents running on IBM Z or IBM i systems to specific targets. It runs on either Windows or Linux. |
| Ironstream Hub Portal | Hub Portal | The web browser-based user interface where Ironstream data pipelines are configured. |
| Ironstream® Agent for IBM i | IBM i Agent | Software on an IBM i LPAR that generates messages that can be received by Hub. |
| Ironstream® Agent for IBM Z | IBM Z Agent | Software in an IBM z/OS LPAR that generates messages that can be received by Hub. |
| Ironstream® for IBM i Configuration Tool | Configuration Tool |
A web browser-based user interface that provides a single location for defining the connection and collection details for IBM i Agents.
Note: IBM Z Agents are not configured using this tool. Those settings are defined in the LPAR itself. See the Ironstream for Splunk for IBM Z Configuration and User Guide for details on how define what data is sent to Hub from an IBM Z LPAR.
|
| Hub Service | Hub Service | The Service that is created, as part of the installation process, to run Hub. |
| Record | – | A Record is a single set of data in a Hub Pipeline. Records can be in raw, JSON, CSV or other formats. Events and messages can be called Records. |
| Pipeline | – | Pipelines define how data moves from a Source through Processes to Data Targets. |
| Source | – | A Source is the origin of the data or records that are being collected. Sources are currently limited to IBM Z and IBM i systems running Ironstream agents. A pipeline will always start with a Source. |
| Target | – | A Target is the ultimate destination for the data, and it is the end point of a Pipeline. Example Targets include Kafka, Google Security Operations, and IBM QRadar. More generic Targets like TCP/IP and HTTP[S] allow data to be forwarded to other platforms such as Splunk, DataDog, and Big Panda. |
| Process | – | A Process is a function to process data. Processes can extract, filter, transform, aggregate, and filter data. |
| Routing | – | Routing refers to the method Hub uses to join a Source, an arbitrary number of Processes and an arbitrary number of targets into one or more Pipelines. |