Skip to main content

Best Practices in Logging

By Gourav S

Summery :


  •  Follow best practices in logging, such as avoiding logging sensitive information and using appropriate log levels for different scenarios.
  • use asynchronous logging over synchronous with a minimum logging level of WARN for a production application. In some cases, enable INFO logging level when you need to confirm events such as successful policy installation or to perform troubleshooting.
  • Avoid logging sensitive information.
  • Using correlation identifier to trace system calls across application layers.
  • Use categories to turn on/off logging during runtime, for eg we need diff. log level for Dev & PROD.
  •  If a flow uses several loggers, add some fixed text in the logger’s message to identify where it was generated. 


Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

Microservices design patterns

By Gourav S
Microservices design pattern Next :  saga-design-pattern-microservices
Post a Comment
Read more

Integration Design Patterns

By Gourav S
Understanding Integration Design Patterns: Integration design patterns serve as reusable templates for solving common integration problems encountered in software development. They encapsulate best practices and proven solutions, empowering developers to architect complex systems with confidence. These patterns abstract away the complexities of integration, promoting modularity, flexibility, and interoperability across components. Most Common Integration Design Patterns: Point-to-Point Integration: Point-to-Point Integration involves establishing direct connections between individual components. While simple to implement, this pattern can lead to tight coupling and scalability issues as the number of connections grows. Visualizing this pattern, imagine a network of interconnected nodes, each communicating directly with specific endpoints. Publish-Subscribe (Pub/Sub) Integration: Pub/Sub Integration decouples producers of data (publishers) from consumers (subscribers) through a central ...
Post a Comment
Read more

Introduction to MuleSoft

By Gourav S
Mule ESB is a lightweight and highly scalable Java-based enterprise service bus (ESB) and integration platform provided by MuleSoft. Mule ESB allows the developer to connect applications easily and quickly. Regardless of various technologies used by applications, Mule ESB enables easy integration of applications, enabling them to exchange data. Mule ESB has the following two editions: Community Edition. Enterprise Edition. What is API-led connectivity? API-led connectivity  is a methodical way to connect data to applications through reusable and purposeful APIs within an organisation’s ecosystem. These APIs are developed to play a specific role: unlocking data from systems, composing data into processes, or delivering an experience.  What are the 3 APIs that enable API-led connectivity?  API-led connectivity provides an approach for connecting and exposing building blocks in an ecosystem. Their scope can vary: within a specific domain, within a line of business (LoB), acr...
Post a Comment
Read more