We are currently tracking file stats by storing them in a file in file-stats engine's sandbox. This is neither flexible, nor standard, nor scalable - it was just proof of concept. We need to sink all the logging, including such things that file-stats now captures and put it into a common storage (e.g. ElasticSearch). My first idea would be to try to integrate ELK (Elastic-Logstash-Kibana) which would give us storage, visualization and flexible storage sink. But only logstash could be exposed to lazy with everything else being abstracted.
We are currently tracking file stats by storing them in a file in
file-stats
engine's sandbox. This is neither flexible, nor standard, nor scalable - it was just proof of concept. We need to sink all the logging, including such things thatfile-stats
now captures and put it into a common storage (e.g. ElasticSearch). My first idea would be to try to integrate ELK (Elastic-Logstash-Kibana) which would give us storage, visualization and flexible storage sink. But only logstash could be exposed to lazy with everything else being abstracted.