Implement a message queue for logging in a .NET webapi

I have a .NET7 server, with a few webapi, that logs the request and responses to log files with NLog.
I don't want to waste time on the logging, so in the controllers I add the message to a

  ConcurrentQueue<LogText> logTextsQueque

this way

  var logText = new LogText { deviceSerial= deviceSerial, message = message };   
  logTextsQueque.Enqueue(logText);  

and in the Main.cs I added this loop, that effectively writes the log to disk:

    _ = Task.Run(async () =>
            {
                while (true)
                {
                    try
                    {
                        if (logTextsQueque.TryDequeue(out LogText result))
                        {
                            LogOut(result.deviceSerial, result.message);
                        }
                        
                    }
                    catch (Exception ex)
                    {
                        LogManager.GetCurrentClassLogger().Error($"C3 Background thread error: {ex.Message}");
                    }
                    finally
                    {
                    }
                }
            });

It's a sort of message queue. It seems to be working, but is there something I should be worried about with this simple implementation?

Thanks

NLog has a builtin message-queue called AsyncWrapper, that can be easily enabled in NLog.config using <targets async="true">:

By default it uses overflowAction="Discard" to prevent application failure because of logging issues.

The AsyncWrapper ensures that NLog Context will correctly capture ${threadid} and will log the threadid of the application-thread (and not the background thread handling the message-queue).