On 22/12/17 01:27, David Holmes wrote:
cc'ing net-dev as that might be the more appropriate list.
On 22/12/2017 10:59 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 4:35 PM, David Holmes
wrote:
On 22/12/2017 10:29 AM, Steven Schlansker wrote:
On Dec 21, 2017, at 11:11 AM, Steven Schlansk
As someone who works with alot of log files, I'd like to chime in and
support Steven's end goal. Looking at a "Connection refused" error in
the middle of a log file that possibly extends to millions of lines is
near useless. In the era of cloud compute, diagnosing network issues is
sure to beco
On 22/12/17 14:59, Seán Coffey wrote:
As someone who works with alot of log files, I'd like to chime in and
support Steven's end goal. Looking at a "Connection refused" error in
the middle of a log file that possibly extends to millions of lines is
near useless. In the era of cloud compute, di
Hello,
I also dearly miss Socket addresses in connection exceptions, however it looks
like it is not going to make it. However if we add a getter for the Peer
address (not included in toString) then logging frameworks could detect
instances of ConnectException and process them accordingly.
Gru
