7206de9c2a
- an exporter is no longer fixed construct. Instead, this commit creates an `Exporter` abstraction. An exporter has a type and is responsible for exporting marvel documents. - multiple exporters can be configured, each can be of a different type. - an exporter can be of a "singleton" type, indicating that there can only be one exporter of that type at any point in time. - exporters are configured in the settings. Each exporters is identified by a unique name/id and has its own settings (the type of the exporter defines what settings that exporter expects) - exporters are loaded at start up time, but it is also possible to update the exporter settings at runtime (all exporter settings are registered as dynamic cluster settings). When updated, all the exporters will be rebuild & reloaded. - there are two types of exporters: `http` and `local` - `http` exporter exports documents to external elasticsearch clusters using the REST API - the new `http` exporter doesn't support user info as part of the URL (it's pron to security info leak). Instead a new `auth.username` and `auth.password` settings were added that can be set per `http` exporter (when shield is installed, the passwords are filtered out from the node info API) - `local` exporter exports documents to the same cluster the agent is installed on, using the internal node client. - when no exporter is configured, a default `local` exporter is created (for best ootb experience) Original commit: elastic/x-pack-elasticsearch@d1d7c8aefd |
||
---|---|---|
marvel | ||
qa | ||
shield | ||
watcher | ||
x-dev-tools | ||
LICENSE.txt | ||
README.asciidoc | ||
pom.xml |
README.asciidoc
= Elasticsearch X Plugins A set of Elastic's commercial plugins: - License - Shield - Watcher - Marvel