[Part 10] - Build an ASP.NET Core 3.1 Web API and Consume with MVC (Web Api Error Logging)

+++++++++++++++ HURRY (ONLY 24 HOURS LEFT) ++++++++++++++++++++ 🌟 **UDEMY Bestseller Alert Kickstart 2024 with Learning Excellence 🚀**
Exciting news My latest Udemy course has achieved the prestigious "Bestseller" label 🎉

To celebrate, I'm offering an exclusive New Year promotion 🎁 Grab any course for just $9.99 until January 16, 0400 AM (NZT).

🌐 Explore more courses at $9.99 each (Valid till Jan 16):

Feel free to enroll and spread the knowledge among friends and peers who may find these courses valuable

Let's make 2024 a year of learning and growth 🌱

Happy Learning,

As a developer, it would be nice to be able to filter all logs by a certain customer # or transaction #. The goal of structured logging is to solve these sorts of problems and allow additional analytics. Serilog was built with structured logging in mind and makes it easy to record custom object properties and even output your logs to JSON.

I shall build the project from scratch and walk you through the code explaining everything in the process. All the episodes will be in continuation from the previous ones, so it is highly recommended to be up to date with all the previous episodes before viewing this one.

This is part 10 of a multi-part series of tutorials on How to Build a Web API and Consume it in ASP.NET Core MVC using SQL Server and ADO.NET. In this tutorial, I shall discuss the error logging in the Web Api project using the Serilog NuGet package.

Like || Share || Spread || Love

For more updates Follow us on:-