Course Structure

[rsantosdev]

A good outline for an ASP.NET Core logging course focusing on Serilog and SEQ should cover the fundamentals of logging in ASP.NET Core, using Serilog for structured logging, and log aggregation and analysis with SEQ. Here's a suggested outline with topic distribution:

Introduction to ASP.NET Core Logging

1. Overview of ASP.NET Core

   • Importance of logging in web applications
   • ASP.NET Core logging fundamentals and built-in ILogger interface
   • ASP.NET Core Logging Best Practices

2. Structuring log messages effectively

   • Logging exceptions and error handling
   • Log filtering and level control
   • Performance considerations
   • Introduction to Serilog

3. Overview of Serilog and its features

   • Benefits of using Serilog in ASP.NET Core applications
   • Setting up Serilog in an ASP.NET Core project
   • Configuring Serilog output, sinks, and enrichment
   • Serilog in ASP.NET Core

4. Integrating Serilog with the ILogger interface

   • Writing structured log messages with Serilog
   • Using Serilog middleware for request logging
   • Advanced Serilog features (contextual logging, filtering, etc.)

5. Introduction to SEQ

   • Overview of SEQ and its features
   • Benefits of using SEQ for log aggregation and analysis
   • Setting up a SEQ instance (self-hosted or cloud)
   • Integrating Serilog with SEQ

6. Configuring the Serilog SEQ sink

   • Sending log data from ASP.NET Core to SEQ
   • Adding properties and enrichers for better log data analysis
   • Analyzing and Visualizing Logs with SEQ

7. Navigating the SEQ user interface

   • Searching and filtering log data
   • Creating dashboards and visualizations
   • Monitoring and alerting based on log data
   • Course Recap and Further Resources

8. Summary of key concepts and best practices

   • Real-world logging scenarios and examples
   • Further learning resources and next steps

This outline should provide a comprehensive introduction to logging in ASP.NET Core, with a focus on using Serilog and SEQ for structured logging and log analysis.

[rsantosdev]

Should we add topics for Functions/WebJobs?

If so a good use case is showing how to track the correlationId from a request that started on asp.net api, then raised a message to a queue and them grab all the logs from the function executing it.

[rsantosdev]

Some reference link: https://benfoster.io/blog/serilog-best-practices