Files

Mingyu Chen fcb651329c [Plugin] Making FE audit module pluggable (#3219 )

Currently we have implemented the plugin framework in FE. 
This CL make the original audit log logic pluggable.
The following classes are mainly implemented:

1. AuditPlugin
    The interface of audit plugin

2. AuditEvent
    An AuditEvent contains all information about an audit event, such as a query, or a connection.

3. AuditEventProcessor
    Audit event processor receive all audit events and deliver them to all installed audit plugins.

This CL implements two audit module plugins:

1. The builtin plugin `AuditLogBuilder`, which act same as the previous logic, to save the 
    audit log to the `fe.audit.log`

2. An optional plugin `AuditLoader`, which will periodically inserts the audit log into a Doris table
    specified by the user. In this way, users can conveniently use SQL to query and analyze this
    audit log table.

Some documents are added:

1. HELP docs of install/uninstall/show plugin.
2. Rename the `README.md` in `fe_plugins/` dir to `plugin-development-manual.md` and move
    it to the `docs/` dir
3. `audit-plugin.md` to introduce the usage of `AuditLoader` plugin.

ISSUE： #3226

2020-04-03 09:53:50 +08:00

1.4 KiB

Raw Blame History

INSTALL PLUGIN

description

To install a plugin

Syntax

    INSTALL PLUGIN FROM [source]
    
    source supports 3 kinds:
    
    1. Point to a zip file with absolute path.
    2. Point to a plugin dir with absolute path.
    3. Point to a http/https download link of zip file.

example

1. Intall a plugin with a local zip file:

    INSTALL PLUGIN FROM "/home/users/seaven/auditdemo.zip";

2. Intall a plugin with a local dir:

    INSTALL PLUGIN FROM "/home/users/seaven/auditdemo/";

2. Download and install a plugin:

    INSTALL PLUGIN FROM "http://mywebsite.com/plugin.zip";

keyword

INSTALL,PLUGIN

1.4 KiB Raw Blame History

INSTALL PLUGIN

description

example

keyword

1.4 KiB

Raw Blame History