This document outlines the agenda for the Chicago MuleSoft Meetup on September 18, 2019. The agenda includes introductions from Redwood Logistics and Big Compass, a presentation on Redwood's logging story and practices, a demo of logging with Log4j2 and ELK, and a discussion of Redwood's future vision which includes becoming a more data-driven organization.

1. Chicago MuleSoft Meetup
September 18, 2019

2. Chicago MuleSoft Meetup
September 18, 2019

3. Agenda
• 6:00PM – Doors open
• 6:00PM - 6:30PM – Network, Eat, and Socialize
• 6:30PM - 6:40PM – Introductions and Redwood Logistics' Story
• 6:40PM - 7:15PM – Logging
• 7:15PM - 7:30PM – Future State of Logging
• 7:30PM - 7:45PM – Q&A
• 7:45PM - 8:00PM – Open Floor, Suggestions for Future Topics and
Speakers
3

4. Introductions
• About the presenters:
• Redwood
• Eric Rempel, Chief Innovation Officer
• Big Compass
• Aaron Lieberman, MuleSoft Practice Manager and Lead Consultant
4

5. More Than Just Logging
• Redwood Logistics’ Logging Story
• The Importance of Logging
• Common Logging Mistakes
• MuleSoft Logging With Log4j2
• Logging to Different Target Systems
• Gaining Value Out of Logged Data With Redwood
• Redwood’s Future State

6. Redwood Logistics Story
6

7. Redwood Logistics’ Transformation
• Difficult to Support -> Deep
Visibility
• Reactive -> Proactive
7

8. Giveaway!

9. Why Log In The First Place?
• System visibility
• System traceability
• Supportability
• Debugging
9

10. Common Logging Mistakes
• No logging standards
• Hard coding
• Empty loggers
• Beware! CloudHub logs are limited by size
• 100MB or 30 days, whichever comes first
10

11. Logging Best Practices
• Standards, standards, standards
• JSON
• Key-value pairs
• Other formats
• Informative messages
• Visibility into the system
• Enhance debugging
• Before and after external system calls
• Request identifier
• Trace transaction from end to end
• Ability to calculate latency
11

12. Logging Best Practices Continued
• Dynamic error messages
• Persisting logs to a system
• Maintain historical logs
• Allows non-technical users to access and support applications
• Not too much logging, not too little
12

13. Demo!
Logging Common
Mistakes and How
To Fix Them

14. Logging With Log4j2
• MuleSoft logging power unlocked
with Log4j2
14

15. How Does Log4j2 Work?
15

16. Architecture - Log4j2 to ELK Stack
16

17. Demo!
Logging With Log4j2
and ELK and Gaining
Value out of Logged
Data

18. Giveaway!

19. Data = POWER!
• Logging to a centralized data
warehouse allows us to
• Gain deep visibility
• Expose data to customers securely
• Expose data internally
• Support any needs from across the
business on the core platform
• Become a data driven organization
19

20. Current Logging Architecture
20

21. What Does the Future Hold For Redwood?
• Ideal Architecture
• Logging Possibilities
• Loggly
• ELK
• Splunk
• Griffana
• Visualization Tools
• Tableau
• Looker
• Let the Data Drive Decisions
• Becoming a data driven organization
• Leading to Blockchain in Logistics
21

22. Questions?

23. Wrap Up
• Contact/Follow Us!
• Big Compass
• https://www.bigcompass.com
• LinkedIn - https://www.linkedin.com/company/big-compass/
• Twitter - https://twitter.com/big_compass
• Facebook - https://www.facebook.com/bigcompass/
• Redwood Logistics
• https://www.redwoodlogistics.com
• LinkedIn - https://www.linkedin.com/company/redwood-logistics-/
• Twitter - https://twitter.com/redwoodlgistics
• Facebook - https://www.facebook.com/redwoodlgistics/
• Aaron Lieberman
• https://www.linkedin.com/in/aaron-lieberman-8a89bb46/
• Eric Rempel
• https://www.linkedin.com/in/ericrempel/
• https://twitter.com/rempel?lang=en
23

24. References and Documentation
• Demo Project Code
• Logging project code: https://github.com/BigCompass/mulesoft-meetup-
logging-demo
• Log4j2
• Apache documentation: https://logging.apache.org/log4j/2.x/
• MuleSoft Documentation: https://docs.mulesoft.com/runtime-
manager/custom-log-appender
• Deploying to CloudHub
• Disable CloudHub logging to allow Log4j2 configuration to take over
• Documentation: https://docs.mulesoft.com/runtime-manager/custom-log-appender
24

25. What’s Next?
• Share:
• Share on social media with any pictures with the hashtag #MuleMeetup
• Invite your network to join: https://meetups.mulesoft.com/chicago/
• Feedback:
• Contact your organizer to suggest topics
• Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
• Our next meetup:
• Date: TBD
• Location: TBD
• Topic: TBD
25

26. See you next time
• Please send topic suggestions to the organizer