Documentation

7.16. Account interaction¶

The account-interaction event handler is used to detect when one account operates on files that are accessible to another account.

It can detect files that are directly configured to an account or inherited from the group. It detects any file, recursively, both in the home folder path as well as in any shared virtual directories.

It will emit the event with ID 20193 for each operation on any file available to other accounts, as long as those accounts are enabled. It will not emit the event 20193 for itself.

Events are only emitted for file operations. Directory operations are ignored. Get in touch if you need to receive events for directory operations.

It can be used to trigger email notifications between members of the team or trigger any other file management operation.

7.16.1. name ¶

Default value:

Optional:

From version:

2.10.0

Values:

Any text.

Description:

Human-readable short text used to identify this event handler.

7.16.2. description ¶

Default value:

Optional:

Yes

From version:

2.10.0

Values:

Any text.

Description:

Human-readable text that describes the purpose of this event handler.

7.16.3. type ¶

Default value:

Optional:

From version:

2.10.0

Values:

file-dispatcher - Dispatch a file into one or multiple paths.
http - HTTP POST request (unsecured).
local-file - Append events to a file located on the local file system.
email-sender - Send emails as an SMTP client.
windows-eventlog - Send events to Windows EventLog Service.
standard-stream - Send events to standard output.
syslog - Local Unix socket or remote IP:PORT address for Syslog.
create-archive - Create/Compresses one or more files.
extract-archive - Extract/Uncompressed a file.
external-executable - Execute an external script or program.
openpgp - Encrypt/Decrypt files using OpenPGP.
rabbitmq - Publish event to RabbitMQ AMQP 0-9-1 server.
extension - For custom event handlers implemented using our API.

Description:

This option specifies the type of the event handler. Each type has a set of specific configuration options.

7.16.4. target ¶

Default value:

Optional:

Yes

Values:

Comma separated list of event ids.
Comma separated list of event ids starting with an exclamation mark.
Leave empty to handle all events.

From version:

2.10.0

Description:

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.

Note

Combining the two methods is not supported as the same result can be achieved by allowing only the desired events, all the others will be ignored.

7.16.5. groups ¶

Default value:

Optional:

Yes

Values:

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

From version:

3.39.0

Description:

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.

7.16.6. usernames ¶

Default value:

Optional:

Yes

Values:

Comma separated list of usernames.
Comma separated list of usernames starting with an exclamation mark.
Leave empty to handle all events.

From version:

3.9.0

Description:

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.

7.16.7. components ¶

Default value:

Optional:

Yes

Values:

Comma separated list of UUIDs.
Comma separated list of UUIDs starting with an exclamation mark.
Leave empty to handle all events.

From version:

3.18.0

Description:

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.

7.16.8. source_addresses ¶

Default value:

Empty

Optional:

Yes

Values:

Comma separated list of IP addresses.
List of IP addresses starting with an exclamation mark.
Empty.

From version:

3.40.0

Description:

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.

7.16.9. data_filter ¶

Default value:

Optional:

Yes

Values:

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.

From version:

3.22.0

Description:

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.

7.16.10. fail_after_errors ¶

Default value:

Optional:

Yes

From version:

3.0.0

Values:

An integer number greater than 0.
0 Disabled.

Description:

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.

7.16.11. monitored_operations ¶

Default value:

all

Optional:

Yes

Values:

Comma-separated values.
all
created
deleted
read
moved
modified

From version:

4.25.0

Description:

Comma-separated list of file operations for which to emit notification events.

Set it to all for emitting events for any file operation. When left empty, it will default to all. When all is set, any other configured value is ignored and will emit events for any file operation.

The read operation is for file downloads. The read operation is not supported for the local filesystem monitor service.

The modified interaction notification is only supported for the local filesystem monitor service.

7.15. File message digest generator

7.17. Extension API