MQTTnet VS serilog-sinks-console

MQTT https://github.com/dotnet/MQTTnet

MQTTNet - High perf IOT comms for .NET - https://github.com/dotnet/MQTTnet

I'm trying to use MQTT.Net and so far everything works.. except for event handling.

Like the other guy said it depends on the requirements, but you could implement your own mqtt server with MQTTnet with a few lines of code

For the server we used mosquitto because we already used it in the past (and it's relatively simple), for the client MQTTnet because it's .net and it seemed good enough (mosquitto has a client library too but it's C so I'd have to write some interop). It's a simple protocol so it shouldn't really matter which implementation you use.

We are going to use MQTTNet as the foundation for this article, although the same concepts can be applied with any other MQTT client.

[2] https://github.com/dotnet/MQTTnet

For example, I used MQTTnet which is a very nice (high performance & extensible) library. And it's free/open source. If you're not writing your server code in .NET, then look for whatever broker libraries are available on your server platform.

The following built-in themes are available

This is best handled as a display issue. It will depend on how you are configuring serilog. Where are you seeing these messages - on a console? Are you using a console logger such as https://github.com/serilog/serilog-sinks-console

Serilog.Sinks.Console – To write log events to the Windows Console or an ANSI terminal via standard output

MQTTNet MQTTnet.Extensions.ManagedClient Serilog Serilog.Sinks.Console Newtonsoft.Json