If the internal HttpClient instance does not idle for a sufficiently long period of time, the DNS name for the Seq instance will never be resolved after the initial resolution.
This causes the forwarder instance to miss changes to the Seq server's IP address if the fowarder remains busy.
I suggest adding a TimeSpan named PooledConnectionLifetime field in the SeqForwarderOutputConfig. During the registration of the HttpClient instance, use the configured TimeSpan value to set the PooledConnectionLifetime property of the SocketsHttpHandler.
I would be happy to provide a pull request, if you are interested.
If the internal HttpClient instance does not idle for a sufficiently long period of time, the DNS name for the Seq instance will never be resolved after the initial resolution.
This causes the forwarder instance to miss changes to the Seq server's IP address if the fowarder remains busy.
I suggest adding a TimeSpan named PooledConnectionLifetime field in the SeqForwarderOutputConfig. During the registration of the HttpClient instance, use the configured TimeSpan value to set the PooledConnectionLifetime property of the SocketsHttpHandler.
I would be happy to provide a pull request, if you are interested.