SEQ logger in disconnected mode endlessly fills queue

[peter-friedland-t2i]

Giving the following scenario:

1. Seq logger instance created and initialized
2. No SEQ server is running. Error is printed out
3. Sending log messages are queued but never send

As a reseult, the memory usage just grows. I did not found option to check if the logger is connected to the seq server and e.g. do not send messages or even that the library checks that.

Whats the proposed solution here?

[Jamminroot]

Hey, thanks for letting me know. And yeah, didn't really look into this library for quite a while now, but I don't think this scenario is covered.
There is no built-in solution for this, and only option would be to check if the endpoint is available before library inits and starts queueing events to-be-sent.

Not giving any promises, but I'll try to have a look at this when I get some free time; Or, you can suggest your code as a PR, and I'd be happy to accept it