Hacker News new | ask | show | jobs
by wiz21c 191 days ago
Lots of network engineer don't understand the usefulness of a stack trace.

IOW: when my network fails "No route to host", I want to know who failed and why. Not just "hey, start the route tool on your production sever which you don't have access to, to get to know who slipped"

1 comments

You're kind of proving the articles point here. The networking stack doesn't surface that information to your code, because it doesn't have that information. To get that information, The various tools do a lot of extra things that don't typically happen on a normal network connection. This is kind of the like complaining that your typical release build stack trace doesn't also include profiling and debug information in it.