This plugin allows to store SFTPGo filesystem and provider events in supported database engines. It is not meant to react to pre-* events.
The plugin can be configured within the plugins section of the SFTPGo configuration file. To start the plugin you have to use the serve subcommand. Here is the usage.
NAME:
sftpgo-plugin-eventstore serve - Launch the SFTPGo plugin, it must be called from an SFTPGo instance
USAGE:
sftpgo-plugin-eventstore serve [command options]
OPTIONS:
--driver value Database driver (required) [$SFTPGO_PLUGIN_EVENTSTORE_DRIVER]
--dsn value Data source URI (required) [$SFTPGO_PLUGIN_EVENTSTORE_DSN]
--custom-tls value Custom TLS config for MySQL driver (optional) [$SFTPGO_PLUGIN_EVENTSTORE_CUSTOM_TLS]
--pool-size value Naximum number of open database connections (default: 0) [$SFTPGO_PLUGIN_EVENTSTORE_POOL_SIZE]
--instance-id value Instance identifier [$SFTPGO_PLUGIN_EVENTSTORE_INSTANCE_ID]
--retention value Events older than the specified number of hours will be deleted. 0 means no events will be deleted (default: 0) [$SFTPGO_PLUGIN_EVENTSTORE_RETENTION]
--help, -h show helpThe driver and dsn flags are required. The instance-id allows to set an identifier, it is useful if you are storing events from multiple SFTPGo instances and want to store where they are coming from.
If you set a retention > 0 events older than now - retention (in hours) will be automatically deleted. Old events will be checked every hour.
Each flag can also be set using environment variables, for example the DSN can be set using the SFTPGO_PLUGIN_EVENTSTORE_DSN environment variable.
This is an example configuration.
...
"plugins": [
{
"type": "notifier",
"notifier_options": {
"fs_events": [
"download",
"upload",
"delete",
"rename",
"mkdir",
"rmdir",
"ssh_cmd"
],
"provider_events": [
"add",
"update",
"delete"
],
"provider_objects": [
"user",
"folder",
"group",
"admin",
"api_key",
"share",
"event_action",
"event_rule",
"role",
"ip_list_entry",
"configs"
],
"log_events": [
1,
2,
3,
4
],
"retry_max_time": 60,
"retry_queue_max_size": 1000
},
"cmd": "<path to sftpgo-plugin-eventstore>",
"args": ["serve", "--driver", "postgres"],
"sha256sum": "",
"auto_mtls": true
}
]
...With the above example the plugin is configured to connect to PostgreSQL. We set the DSN using the SFTPGO_PLUGIN_EVENTSTORE_DSN environment variable.
The plugin will not start if it fails to connect to the configured database service, this will prevent SFTPGo from starting.
SFTPGo will automatically restart it if it crashes and you can configure SFTPGo to retry failed events until they are older than a configurable time (60 seconds in the above example). This way no event is lost.
The plugin supports also the migrate and reset sub-commands that can be used in standalone mode and are useful for debugging purposes. Please refer to their help texts for usage.
The plugin will automatically create the following database tables:
eventstore_fs_eventseventstore_provider_eventseventstore_log_events
Inspect your database for more details.
To use Postgres you have to use postgres as driver. If you have a database named sftpgo_events on localhost and you want to connect to it using the user sftpgo with the password sftpgopass you can use a DSN like the following one.
"host='127.0.0.1' port=5432 dbname='sftpgo_events' user='sftpgo' password='sftpgopass' sslmode=disable connect_timeout=10"Please refer to the documentation here for details about the dsn.
To use MariaDB/MySQL you have to use mysql as driver. If you have a database named sftpgo_events on localhost and you want to connect to it using the user sftpgo with the password sftpgopass you can use a DSN like the following one.
"sftpgo:sftpgopass@tcp([127.0.0.1]:3306)/sftpgo_events?collation=utf8mb4_unicode_ci&interpolateParams=true&timeout=10s&tls=false&writeTimeout=30s&readTimeout=30s&parseTime=true&clientFoundRows=true"Please refer to the documentation here for details about the dsn.