etcdevteam / geth-elk Goto Github PK

indexes are the forking point for visualizations, searches, and dashes. relying on indexes to manage the data between various contributing clients will be a nightmare.

to save a lot of tedious time and complexity, I think it'll be good to configure the logstash configuration file to deduce and define a unique key for each contributing source, like client: hostname-ip or something like that.

another option is to add this as an "always-on" field in the geth's mlog output, but i think better to delegate this responsibility to log management instead of creation

see elastic/kibana#3668

maybe etc-<chainname>-YYYY.MM.DD