meetup

2. Helsinki, Finland meetup #2
September 25th, 2020
Logging Best Practices in Enterprise
Environment

3. Introduction

4. All contents © MuleSoft Inc.
• Senior Integration Architect at TCS
• MuleSoft Meetup Leader for Helsinki, Finland and
Bangalore, India.
• Working with MuleSoft products for over 7 years now
• Certified MuleSoft Integration Architect and platform
Architect
• Certified MCD – Integration Professional
• Certified MuleSoft Developer
• LinkedIn: https://www.linkedin.com/in/rajeshdns/
Organizer Rajesh Kumar

5. All contents © MuleSoft Inc.
• Integration Specialist at Solita
• Working with integrations 6+ years, 5 years in health
sector
• Certified Certified Developer and API Design
Associate
• LinkedIn: https://www.linkedin.com/in/juha-niskala/
Speaker Juha Niskala

6. All contents © MuleSoft Inc.
Agenda
6
17:00 PM - 17:15 PM : Introduction, networking
17:15 PM - 18:00 PM : Loggin Best Practices in Enterprise Environment
18:00 PM - 18:15 PM : QA Session
18:15 PM - 18:30 PM : Trivia Quiz , wrap up (next Meetup and topic)

7. All contents © MuleSoft Inc.
Helsinki MuleSoft Meetup Group
7
• https://meetups.mulesoft.com/he
lsinki/
• Why?
– Suggest topics
– Discuss event’s topics
– Discuss anything you like
– Ask questions
– See updates regarding our
group!
Register today 

8. Logging best practices
in Enterprise Environment

9. All contents © MuleSoft Inc. 9
• Agenda
– Quick dive into EE and what it is
– We all have different log styles
– Did you know that there are log levels
– Can there be excessive logging?
– How to take care of different stakeholders
– Let’s talk about strategy of logging
– Finally there are best practices that we should know about
Logging Best Practices in Enterprise
Environment

10. All contents © MuleSoft Inc. 10
• Characteristics of EE
– Network of complex systems
• SAP, Salesforce, etc.
– Managed systems, networks, etc.
• Databases, VPNs, etc.
– Vast amount of integrations
– 24/7 monitoring
– Dedicated support and development
– Some sensitive data
Logging Best Practices in Enterprise
Environment

11. All contents © MuleSoft Inc. 11
• Different log styles
• Logs usually vary by many factors
– Developer, guidelines, maturity, etc.
– Pressure, time allowed to polish
– Tools capabilities
Logging Best Practices in Enterprise
Environment

12. All contents © MuleSoft Inc. 12
• Log levels
• Are errors always errors?
• Warnings are your friend
• Detailed log in debug or even trace
– Not all levels need to be enabled in log4j2
Logging Best Practices in Enterprise
Environment
Fatal •Least verbose
Error
Warn
Info •Default log level
Debug
Trace •Most verbose

13. All contents © MuleSoft Inc. 13
• Excessive logging?
– 1.440 times in a day
– 10.080 times in a week
– 525.600 times in a year
Logging Best Practices in Enterprise
Environment

14. All contents © MuleSoft Inc. 14
• Excessive logging?
– 1.440 times in a day
– 10.080 times in a week
– 525.600 times in a year
• How to solve?
– Log only errors?
– 1.440 + errors in a day
Logging Best Practices in Enterprise
Environment

15. All contents © MuleSoft Inc. 15
• Excessive logging?
– 1.440 times in a day
– 10.080 times in a week
– 525.600 times in a year
• How to solve?
– Log only errors?
– How about problem solving?
• With payload 100
– 145.440 + errors in a day
Logging Best Practices in Enterprise
Environment

16. All contents © MuleSoft Inc. 16
• Excessive logging?
– 1.440 times in a day
– 10.080 times in a week
– 525.600 times in a year
• With payload of 100
– 144.000 times in a day
+ all errors
– Still a lot
Logging Best Practices in Enterprise
Environment

17. All contents © MuleSoft Inc. 17
• Excessive logging?
• Need to consider what is relevant
• Do you really have to know
if something went thru?
• Or just failed ones?
• No need to log received payload?
• It is a game of balance
Logging Best Practices in Enterprise
Environment
More Less
Readability
Performance
Costs
Legal
Guaranteed
delivery
Context

18. All contents © MuleSoft Inc. 18
• Stakeholders
– Who are the people asking questions?
– Did order xyz go to system A
– Data ownership/restrictions – when logging payload
• Integrations are between systems therefore someone is interested
about data
– Try to solve during development most relevant support cases and try to
overcome with brilliant logging
• Knit together multiple apps or even systems with correlationIds
– Not always need to use Mule’s generated correlationId
– Can be unique document id from source system
Logging Best Practices in Enterprise
Environment

19. All contents © MuleSoft Inc. 19
• Custom logger
– When logging becomes too complex to handle with default logger component
– Requires often external logging system
• Not always needed since
– Log4J2 can handle some nifty stuff
Logging Best Practices in Enterprise
Environment

20. All contents © MuleSoft Inc. 20
• Logging strategy
– Do this once and reuse
– Should give answer to questions
• What to log / What not to log?
• Where to log?
• Sensitive data handling?
Logging Best Practices in Enterprise
Environment

21. All contents © MuleSoft Inc. 21
• Best practices
1. Plan ahead and create a big picture how to do logging – Logging strategy
2. Take in consideration of whole picture and utilize chaining systems together
with correlationId and readable logs – Chain complex systems together
3. Keep logging simple and streamlined so it won’t be bottleneck for solution and
your support personnel will thank you – Keep logs readable and simple
4. Logging and sample of logs should be reviewed not by developer but also by
support personnel as they know if it is enough – Review logs
Logging Best Practices in Enterprise
Environment

22. All contents © MuleSoft Inc.
CHEERS..!!
22
We have prizes to give away!
For 3 Winners special prize is ready
A SHOW OF HANDS:
New Members With Us.!!

23. All contents © MuleSoft Inc. 23
1. What can you use to knit together multiple systems and
integrations?

24. All contents © MuleSoft Inc. 24
3. What is the most verbose log level of logging?

25. All contents © MuleSoft Inc. 25
5. There are two different ways of logging. One of them stops
everything while the other let’s app moving forward. What these
two are?

26. Questions & Answers
Discussion
26

27. All contents © MuleSoft Inc. 27
• Feedback:
– Contact your organizer D.Rajeshkumar via e-mail (meetup page) or LinkedIn
profile(https://www.linkedin.com/in/rajeshdns/) to suggest topics
– Contact MuleSoft at meetup@mulesoft.com for ways to improve the program
• Our next meetup:
– Date: Q4 2020
– Topic: not known yet
What’s next

28. See you next time