Skip to content
This repository was archived by the owner on Sep 8, 2025. It is now read-only.

Commit c27b1af

Browse files
Update src/content/posts/2024-07-24-logging-messages.md
thanks! Co-authored-by: schilco-rimdev <[email protected]>
1 parent 5d8a140 commit c27b1af

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/posts/2024-07-24-logging-messages.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Admittedly, I didn't know as much about logging as I should have 🤷🏻‍♂
2929

3030
ASP.NET Core makes it easy to connect to a variety of logging providers. You can find out more about setting up logging [here](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/logging/?view=aspnetcore-8.0). I want to focus on the messages you pass to the logger.
3131

32-
The messages get passed using a message template. This allows for [symantic or structured logging](https://github.com/NLog/NLog/wiki/How-to-use-structured-logging). I read that was important because logging providers can store the parameters in the message template as fields. What does that look like and why is that important? Sometimes I need to see it in action to cement my understanding.
32+
The messages get passed using a message template. This allows for [semantic or structured logging](https://github.com/NLog/NLog/wiki/How-to-use-structured-logging). I read that was important because logging providers can store the parameters in the message template as fields. What does that look like and why is that important? Sometimes I need to see it in action to cement my understanding.
3333

3434
I ran `dotnet new webapp` to setup a new ASP.NET Core project. In the project's Program.cs file I added this contrived endpoint:
3535

0 commit comments

Comments
 (0)