Enhancement: Allow for using of Elasticsearch index template instead of using built in index pattern

[BenB196]

Currently field names are locked into the ones given by Crashplan FFS. However a lot of these fields don't make usable sense when trying to integrate with other indexes (ex: osHostname should really be either hostname or host, and deviceUsername should be username).

Should allow for people to create custom mappings so that they can integrate the FFS into their own indexes.

[BenB196]

This can be achieved using a map:

map[string]interface{}

[BenB196]

Possibly use https://www.elastic.co/guide/en/elasticsearch/reference/current/alias.html as a stop gap until this feature is fully implemented.

[BenB196]

This is actually solving the wrong problem. The real problem is that this should not create the index with mappings. Instead an index template should be used on the elasticsearch end.

TODOs:

• Develop base Elasticsearch Index Template
• Add option to disable index creation with index pattern in configuration

[BenB196]

Added in release v0.0.9.