We all love spending one full week writing code. I'm pretty sure you wouldn't like spending one week trying to figure out the root cause of a bug, especially if you can't rely on logs.

So, here's the first step: write some logs. How?

Next: where can we store them?

In this session, you will learn why logging is one of the most crucial (yet underestimated) parts of any software system. You will meet some logging best practices, and you will learn how to use Serilog as a library for logs on steroids.

We will talk about:
- Why logging is more important than you think;
- Logging, with pros and cons;
- How to log on Console with .NET;
- How to integrate Serilog in our .NET applications;
- How to integrate SEQ to store our logs, query the data, and create custom dashboards.

After this session, you will be able to understand if your logging strategy is effective, how to improve it, and how to integrate Serilog and SEQ for storing and analyzing logs.

The ideal session duration is 40 minutes.
If necessary, I can add more topics to make it fit a 1-hour slot.

This session includes some real examples and some live coding. I will need to have access to an Internet connection.