The seed of this is thinking about Docker and Debugging, so I’ll throw : https://github.com/docker/labs/blob/master/developer-tools/java-debugging/IntelliJ-README.md on the pile.
On February 8, 2017 at 12:32:45, Otto Fowler (ottobackwa...@gmail.com) wrote: Yes. In general I can see something like this flow General Idea/Whitepaper/article -> reference only in doc, maybe we have a “Links of interest” or something Metron specific article derived from and augmented that references the above in doc So we have a way of approving and listing external articles that feeds into our ‘implementation’ articles. Does that make any sense? On February 8, 2017 at 11:54:36, zeo...@gmail.com (zeo...@gmail.com) wrote: Thanks, I haven't read it yet, but I added it to my reading list. Do you think it would be a good addition to just below this < https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-parsers#notes-on-performance-tuning >, this < https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-enrichment#notes-on-performance-tuning >, and this < https://github.com/apache/incubator-metron/tree/master/metron-platform/metron-indexing#notes-on-performance-tuning > as a "debugging" section? Side note, is it worth unifying this performance tuning guidance somewhere else and generalize it as storm tuning, or is it still worthwhile to be in those areas? I'm good with leaving it as is, just a thought that came to mind... Jon On Wed, Feb 8, 2017 at 11:28 AM Otto Fowler <ottobackwa...@gmail.com> wrote: > Thought this might be interesting as I ran across it > > > https://community.hortonworks.com/articles/36151/debugging-an-apache-storm-topology.html > -- Jon Sent from my mobile device
