Launch Aspire (if it's not already running). See:
In the top section of the Azure Blob Publisher configuration window, specify the description for the publisher.
In the connection section, specify the connection information needed to publish to Azure Blob storage.
In the Binary Objects section, specify the Binary Objects you want to upload related to the connection configuration.
In the Transform Documents section, specify your transform groovy script location, by default it uses the local transform file or Aspire Standard Transform Script.
Use Local Transform File: Mark this option to specify a Transform script (indicated in the JSON Transformation field) to transform the content and store the results of the transformation and unmark this option to specify an uploaded resource fileyou can choose between specifying a Local Transform File or picking from a previously uploaded Resource Transform File:
Local Transform File: the default value is set to "${component.home}/config/groovy/aspireToBlob.groovy" for the default Groovy transformation file provided with Aspire.
This script will be used to transform the data from Aspire as it is posted to the Azure Blob Server
. To use a custom file, follow the instructions in JSON Transformation.
In the Metadata section, specify the metadata configuration.
In the Debug section of the Azure Blob Publisher configuration, specify the Debug flag.
Once you click the add button, the Elasticsearch Publisher settings will be saved.