Configuring Transform Script Process - ironstream_for_splunk - ironstream_for_elastic - ironstream_for_kafka - Ironstream_Hub - 1.3

Ironstream Hub Administration

Product type
Software
Portfolio
Integrate
Product family
Ironstream
Product
Ironstream > Ironstream for Splunk®
Ironstream > Ironstream for Kafka®
Ironstream > Ironstream Hub
Ironstream > Ironstream for Elastic®
Version
1.3
Language
English
ContentType
Administration
Product name
Ironstream Hub
Title
Ironstream Hub Administration
First publish date
2022

The transform script process will process a payload using a particular GoLang script. The yaegi interpreter will be used to execute the script and the scripts will be located in a special scripts directory.

The purpose of the process is to allow users to rapidly add support for new analytics platforms by issuing a new script.

When the ProcessType is set to TransformScriptProcess, a parent field named TransformScriptProcessConfiguration must be populated with one or more pairs of Name and Value fields as shown below. You may have any number of Name and Value pairs as you wish. If you enter items that are not correctly paired, the process will be invalid and the pipeline will not start.
Fields Description Valid Values
ScriptName The name of the script file
  1. Must be at least one character
  2. A file with this name must exist in the scripts directory
  3. The contents of the script must be compilable by the yaegi interpreter
Example Transform Script Process File
{
  "Name": "Script Transform",
  "Id": "bb399413-3c2d-4b45-a85e-bf4c95c9bbc0",
  "ScriptTransformConfiguration": {
    "ScriptName":”TimeSeriesToDataDog”
  },
  "ProcessType": "ScriptTransform"
}