You are doing logging in .NET wrong. Let’s fix it. - Nick Chapsas - NDC London 2024
This talk was recorded at NDC London in London, England. #ndclondon #ndcconferences #developer #softwaredeveloper
Attend the next NDC conference near you:
ndcconferences.com
ndclondon.com/
Subscribe to our KZhead channel and learn every day:
/@NDC
Follow our Social Media!
/ ndcconferences
/ ndc_conferences
/ ndc_conferences
#dotnet #programminglanguage #programming
Logging is a vital part of every application that runs in production. It is in place to tell a story about the lifecycle of its runtime and make it easy for developers to debug a system and identify what failed and how when things go wrong. It is, however, extremely easy to get it wrong, and the problems caused can stay hidden for years. In this session, I will talk you through all the possible issues that logging can cause and show you how you can fix every single one of them.
TL;DW : use Structured Logging (find a library for whatever language you use. It'll add categories to filter on, and data will be put in variables. You can output human readable or json (and use jq to filter your files). Very nice.
I miss the water
nick chapsas with another presentation out of a library's manual. 54 minutes about something that you can find in the first couple of minutes reading the Serilog manpages...
What a pedantic comment
Obviously you didn't watch the video. Or you have some special kind of serilog documentation, because I couldn't find anything about interpolatedstringhandler in the official documentation or wiki.
When making content like this you are forced to assume minimal previous knowledge.
Useless and a waste of time