''

• Comma separated list of event ids.

• Comma separated list of event ids starting with an exclamation mark.

• Leave empty to handle all events.

Define a comma separated list of event ids to have the event handler triggered only for those events.

When you want to have it triggered for all the events, excepting a few events you should prefix each event id with the exclamation mark (!).

Leave it empty to handle all events.

''

• Comma separated list of event groups.

• Comma separated list of event groups starting with an exclamation mark.

• Empty.

Defines the list of event groups for which this handler is active.

When you want to handle all the events, except for the ones from a set of groups, prefix the group names with the exclamation mark (!).

An event can be a member of one or multiple groups. The event is handled if any of its groups is found in the list of configured allowed groups. The event is not handled if any of its groups is found in the list of configured ignored groups (starting with !).

Leave it empty to handle events from all groups.

''

• Comma separated list of usernames.

• Comma separated list of usernames starting with an exclamation mark.

• Leave empty to handle all events.

Comma separated list of usernames whose events are handled by this event handler. A username can include OS accounts, application accounts, and any accounts accepted by any authentication method including external HTTP accounts.

When you want to have it triggered for all the events, excepting a few events you should prefix each username with the exclamation mark (!).

Leave it empty to handle events from any users or events which are not associated with any user.

''

• Comma separated list of UUIDs.

• Comma separated list of UUIDs starting with an exclamation mark.

• Leave empty to handle all events.

Comma separated list of component UUIDs for which events are handled by this event handler.

When you want to have it triggered for all the events, excepting a few events you should prefix each UUID with the exclamation mark (!).

Leave it empty to handle events emitted by any component.

Empty

• Comma separated list of IP addresses.

• List of IP addresses starting with an exclamation mark.

• Empty.

Comma separated list of source IP addresses of the remote peers, which are handled by this event handler.

When you want to have it triggered for all the addresses, excepting a few addresses you should prefix each address with the exclamation mark (!).

Leave it empty to handle events emitted by any source address.

''

• Comma-separated list of data member names and filter expressions.

• Multiple expressions, one per line (Since 4.29.0)

• Leave empty to handle all events.

Comma separated definition with the name of attribute data member and the targeted matching expression.

Data member names are configured with insensitive cases.

For more details about the available expressions see the matching expression documentation.

The following example will extract the value to be matched/filtered from the path data member of the event. The extracted value is then matched against the */folderA/* globbing expression:

[event-handlers/b904ed23-a234-4ccf-8abd-edcae4d3324f]
data_filter = path, */folderA/*

See the usage instructions for more operational details.

You can filter based on multiple data members using multiple rules. Each rule is defined on a separate line.

In the following example, events are triggered only if they are uploaded into the directory named reports-A with a size of 0 bytes (empty file):

[event-handlers/b904ed23-a234-4ccf-8abd-edcae4d3324f]
data_filter =
    path, */reports-A/*
    size, 0

Leave this configuration empty to not filter based on the event's attached data, and handle events regardless of their data attributes.

10

3.0.0

Number of consecutive errors after which the event handler will automatically stop with a failed state.

Setting this to 0 will disable the feature. The event handler will no longer stop regardless of the number of errors encountered.

''

• dispatch-action, file-match-expression, destination-path-1

• dispatch-action, file-match-expression, path-1, path-2

• dispatch-action, file-match-expression

• List of rules, separated by newlines.

This is a comma separated configuration value.

First value is the file dispatching action. The supported actions are:

• move

• move-with-timestamp

• rename

• rename-prepend-unixtime

• delete

• copy

• execute

• ignore

Second value is the the full path matching expression. Globbing expression or regular expression can be used. For more details see the matching expression documentation.

The remaining values are paths to which the file is dispatched. The file is dispatched into the configured destinations observing the configured order. Certain actions do not need a destination path.

When regular expressions are used for the path matching configuration, the destination path can be dynamically generated based on regex matching groups and event specific variables.

The following variables (case-insensitive) are provided as context data containing information about the event being triggered:

• id

• uuid

• message

• account.name

• account.email

• account.peer.address

• account.peer.port

• account.peer.protocol

• account.peer.family

• account.uuid

• component.name

• component.type

• component.uuid

• timestamp.cwa_14051

• timestamp.iso_8601

• timestamp.iso_8601_fractional

• timestamp.iso_8601_local

• timestamp.iso_8601_basic

• timestamp.iso_8601_compact

• timestamp.timestamp

• server.name

• server.uuid

• data.DATA_MEMBER_NAME

• data_json

For more details see the file dispatcher usage guide.

You can specify multiple rules, one per line. Leading and trailing spaces are ignored.

0

4.5.0

This is the number of times a failed file dispatching actions is retried.

When set to 0, failed actions are never retried.

60

4.5.0

Number of seconds to wait before retrying a failed action.

When set to 0, there will be no waiting time. As soon as a file action fails, it will be retried.

30

• Number

Number of seconds to allow for the external process to execute before forcefully closing it.

A configured value must be equal to or greater than 1.

''

• dispatch-action, destination-path-1

• dispatch-action, path-1, path-2

• dispatch-action

This is a comma separated configuration value.

This is a single rule which defines how to dispatch files which were not matched by any of the rules defined at dispatch_rules.

Leave it empty to do nothing for files which don't match any expression.

First value is the file dispatching action. It supports all actions from dispatch_rules.

The remaining values are paths to which the file is dispatched. The files are dispatched using the same process as for dispatch_rules.

''

• attribute name, regular expression

• List of rules, separated by newlines.

This is a comma-separated configuration value.

First value is the name of the attribute from which to collect data for the rename operations.

Second value is the full path matching expression. Globbing expression or regular expression can be used. For more details see the matching expression documentation.

You can specify multiple rules, one per line, to source the rename operation from multiple values. Leading and trailing spaces are ignored.

real_path

• Event data member name.

This is the name of the event's data attribute used to get the path or the list of paths which will be dispatched by this event.

This is a case-insensitive value.

0

• Number of seconds.

Number of seconds to delay the execution of the dispatch action.

If the targeted file no longer exists after the delay, the dispatch execution is canceled and an event is emitted.

Set it to 0 to execute the dispatching right away.

Empty

4.8.0

Allows copying or moving a file to the destination using a temporary name, renaming to its initial name once all the file's content was processed.

Leave it empty to always copy a file to its destination using the original name.

fail

4.8.0

This configuration option is used to decide how to handle the overwriting of an existing file at the destination.

When set to overwrite it will emit an event when the destination file is overwritten.

When set to skip it will not handle the file and the source file is not removed. An event is emitted to inform that the file was skipped.

When set to fail the event handling will fail. The existing file is not overwritten and the source files are not removed.

Empty

• parent

• Empty

This configuration can be used to instruct SFTPPlus to create the destination folder, in case they do not exist.

This is a case-insensitive value.

Set it to parent to create the parent directory of the destination file.

Leave it empty to not have the destination automatically created and fail when the destination does not exist.