I just finished reading it. Looks great Matt! Enjoy giving the presentation!
Remko (Shameless plug) Every java main() method deserves http://picocli.info > On Oct 31, 2017, at 6:26, Ole Ersoy <ole.er...@gmail.com> wrote: > > That's the key - Gotta make it more fun! Keep it fresh - Ziplock fresh! > Freshaliciouss!! > > >> On 10/30/2017 04:14 PM, Matt Sicker wrote: >> Zipkin is a fun topic I wrote a small internal blog post at my client >> about. The general topic I'm doing a talk on is "The How and Why of >> Logging" which is generally aimed at providing an overview of logging >> concepts, common libraries, tools, patterns, etc. Distributed log tracing >> is certainly a topic I was considering talking about in the talk provided >> it doesn't go too long. >> >>> On 30 October 2017 at 15:52, Ole Ersoy <ole.er...@gmail.com> wrote: >>> >>> Probably a series of blog posts :). Another thing that would be great is >>> pumping up some of the new features that log4j2 has that developers will >>> love. It reads a little bit like a theoretical intro to logging in general >>> (Although you did say clearly that that is what it is) and we have a lot of >>> material like that, so what is it about the presentation that should make >>> your peers want to pay attention? I'm sure you'll find that even if the >>> audience have heard of some of the new log4j2 features, they'll appreciate >>> a recap. For example here's a pretty good article on Kotlin that I >>> recently read: >>> >>> http://petersommerhoff.com/dev/kotlin/kotlin-for-java-devs/ >>> >>> A specific example of how to log from both a project dependency, as well >>> as the core project code, would be great as well. The FAQ is good, but it >>> feels a little bit like reading your Denon Receiver's manual ... >>> >>> Could be that throwing in Zipkin (http://zipkin.io/) with the rest of the >>> reference material (Flume, etc.) would be a valued addition. >>> >>> >>>> On 10/30/2017 02:20 PM, Matt Sicker wrote: >>>> >>>> I could spend an entire blog post about Logstash and ELK in general, so I >>>> feel it's out of scope here. >>>> >>>> As for the other questions, I think that's covered by the FAQ < >>>> https://logging.apache.org/log4j/2.x/faq.html>, but if it's not, that >>>> would >>>> be useful here. >>>> >>>> On 30 October 2017 at 13:52, Ole Ersoy <ole.er...@gmail.com> wrote: >>>> >>>> I thought it was very good. I'm a big fan of articles that come with and >>>>> reference simple examples from a github repository. One of the most >>>>> confusing aspects of Java logging is configuring it to use one provider >>>>> when multiple dependencies use different APIs ... SLF4J ... Log4J ... so >>>>> if >>>>> that were included / referenced I think it would be a plus. In case you >>>>> feel like expanding on the integration with Logstash that would be >>>>> awesome >>>>> too. The ELK stack seems to be getting pretty popular. >>>>> >>>>> Cheers, >>>>> >>>>> Ole >>>>> >>>>> >>>>> >>>>> >>>>> On 10/30/2017 01:09 PM, Matt Sicker wrote: >>>>> >>>>> In preparation for an upcoming talk I'll be doing for CJUG, I'm writing a >>>>>> blog post about introductory concepts to logging from both a developer >>>>>> and >>>>>> operator point of view. My current draft is available here: < >>>>>> https://github.com/jvz/jvz.github.io/blob/logging/_posts/201 >>>>>> 7-10-30-logging.md>. >>>>>> Let me know what you think! >>>>>> >>>>>> >>>>>> >> >
