This repository contains two applications. The first one is a console application configured to use Serilog.Sinks.Http, capable of sending log events over the network. The amount of log events, and their size, can be configured using console arguments.
The second application is a ASP.NET Core application acting as a log server, capable of receiving log events sent by the console application. This log server is periodically printing information about received log events and their characteristics.
The applications in the repository have been built to fulfil two use-cases.
Do you know at which rate your application is producing log events? Do you know the average size of a log event? Are you sure that the buffer files won't overflow during peak load?
The HTTP sink can be configured in many ways, but if you are unaware of the logging behavior of your application you have a higher risk of using a configuration that doesn't suit your application. Get to know your application. Let your application send its log events to the log server and get insights into the logging characteristics of your application. Make sure you don't lose those log events during peak load.
Being able to control the amount of log events, and their size, lends itself well to provide a benchmark where we analyze the performance of the sink and the environment it acts within.
Run the following commands to start the console application.
cd ./src/app
dotnet run -- --help
dotnet runRun the following command to start the log server.
cd ./src/log-server
dotnet run