These Actions involve improving raw data using advanced procedures.

Click an Action to learn more about how to use it.

Redis is a powerful in-memory data structure store that can be used as a database, cache, and message broker. It provides high performance, scalability, and versatility, making it a popular choice for real-time applications and data processing.

This action stores data in its cache and makes it available on command.

Find Redis in the Actions tab and drag it onto the canvas to use it.

To use this action, you will need to have access to the Redis service, either on-premise or cloud, installed.

Configuration

Redis Configuration

• Redis endpoint* - enter the endpoint used to establish connection to the redis server.

• Commands - the command to retrieve the data from the server. Choose between SET and GET.

• Redis Key* - if the model has a version, enter it here.

• Event in field - the message to input to redis.

• Output - enter a name for the output event.

Rate Limit

• Maximum requests - set a limit on the number of requests per second to launch on the server.

Click Save to complete.

For each element in the input list, the For Each action generates an output that adds to the input event and the index it occupies in the list.

For example, an input list containing [a,b,c] will generate three outputs, with these fields added to the event:

1. elementValueOutField: a; elementIndexOutField: 0

2. elementValueOutField: b; elementIndexOutField: 1

3. elementValueOutField: c; elementIndexOutField: 2

Find For Each in the Actions tab and drag it onto the canvas to use it.

To open the configuration, click the Action in the canvas and select Configuration

Configuration

• Input* - the field that contains the input list. Valid types areString, Integer, Float, Boolean,Timestamp

• Output Field* - the field where each iterated element will be stored. This will be the same type as the input list field.

• Index Field* - where to stored the index of the returned out field in the input list.

Click Save to complete.

Example

You receive a list type field containing a string of five IPs

127.0.0.1,127.0.0.2,127.0.0.3,127.0.0.4,192.168.0.1.

In the input field, select the list type field.

Assign the value and the index fields a name.

The action will create a separate event for each element of the string, each event containing two fields (value and index).

This action allows you to configure and execute HTTP requests with custom settings for methods, headers, authentication, TLS, and more.

Find Http Request in the Actions tab and drag it onto the canvas to use it.

To open the configuration, click the Action in the canvas and select Configuration.

Configuration

• HTTP Method* - The HTTP method to use for the request (e.g., GET, POST, PUT, DELETE, PATCH).

• Server URL* - The target URL for the HTTP request.

• Payload field - JSON field to include as the request body.

• Output field - Field to store the HTTP response.

• HTTP headers - Key-value pairs for HTTP headers.

• Timeout - Timeout for the request (in seconds, minimum 1).

• Disable redirects - Select true to disable HTTP redirects or false to ignore.

• Content type - Set the request content type (default is application/json).

Authentication Configuration: if you require authentication.

• Authentication type* - None, Basic, Bearer, or API Key.

• Authentication credentials - Credentials required based on the authentication type.

  • Basic Authentication - Username and password for Basic authentication.

  • Bearer token - Token for Bearer authentication.

  • API key: -API key configuration with API Key Name and API Key Value.

Bulk Configuration

• Events per batch - Number of events per batch.

• Store as - Store response with options (Delimited, Without Delimiter, JSON Array).

• Delimiter - Custom delimiter (default is newline).

Rate Limit

• Maximum requests* - set a limit on the number of requests per second to launch on the server.

TLS Configuration

• Certificate - This is the predefined TLS certificate.

• Private Key - The private key of the corresponding certificate.

• CA Chain - The path containing the CA certificates.

• Minimum TLS version - choose the TLS version to use.

Proxy Configuration: if your organization uses proxy servers, establish the connection here.

• Proxy Scheme

• Username

• Password

• URL

Retry Configuration

• Max attempts - Maximum retry attempts.

• Wait between - Wait time (in milliseconds) between attempts.

• Backoff interval - Backoff interval for retries.

Configuration example

{
    "payloadField": "correlationIDKey",
    "outField": "outputField",
    "serverUrl": "http://localhost:8080/${path_from_event}?${impactKey}=${correlationIDKey}",
    "method": "POST",
    "authentication": {
        "authType": "apiKey",
        "credentials": {
            "apiKey": {
                "apiKeyName": "x-api-key",
                "apiKeyValue": {
                    "id": "apiKey",
                    "value": "ad1dewfwef2321323"
                }
            }
        }
    }
}

Click Save to complete.

Evaluate any AI model built with the Cog library and deployed as an endpoint anywhere: SageMaker, HuggingFace, Replicate…

The HttpCog Action seamlessly integrates with models deployed on any platform, including the client's own infrastructure. It enables not only the utilization of state-of-the-art machine learning models but also the execution of code specific to a client's unique use case.

Find Http Enrichment in the Actions tab and drag it onto the canvas to use it.

To open the configuration, click the Action in the canvas and select Configuration.

Configuration

• Endpoint* - enter the endpoint used to establish connection to the model.

• Token - if the model has a token, use it here.

• Version - if the model has a version, enter it here.

• Input* - the message to input to the model.

• Output* - enter a name for the output event.

Click Save to complete.

Overview

This action adds new fields to your events using a given operation. You can select one or more operations to execute, and their resulting values will be set in user-defined event fields.

Find Field Generator in the Actions tab (under the Advanced group) and drag it onto the canvas to use it.

To open the configuration, click the Action in the canvas and select Configuration.

Configuration

You can perform the following operations to define new fields in your events:

Operations

Click Save to complete.