Folks, May I suggest those writing Metron code to get used to use TRACE and DEBUG log levels?
I have recently worked in troubleshooting a mysterious issue involving the indexing topology and quickly noticed we issue a debug message stating a field contains a dot while leaving things like acceptance of message from the connection to kafkaSpout largely invisible. In the spirit of open source I am finishing a PR covering the ElasticSearch indexing topology debugging but I noticed that overall Metron logging isn't particularly verbose, hence my feedback. Storm is already fairly complex to debug[1] so can we try to make Metron a bit more verbose? The user base will only benefit. Cheers [1] by those not particularly familiar with the technology - like me... :-)
