Expose debug info

Open kurin opened this issue 7 years ago • 3 comments

In #41 a user noticed that there was no data going, but didn't have good visibility into what was happening.

Should b2 expose debug info? If so, how?

Mar 06 '18 05:03 kurin

We already have Client.Status(), but getting information out of this requires application authors to take advantage of it. It might be nice to provide either a debug page listening (off the default mux) on a local socket or at least a library that makes it easy to do so.

Mar 06 '18 05:03 kurin

This needs to find a balance between "once you need it, you'll wish you had enabled it" and "don't do weird, unexpected nonsense like put http servers on random sockets."

Mar 06 '18 18:03 kurin

Maybe for now just add ServeHTTP to b2.Client and let app authors call http.Handle("/b2what", client) if they like.

Mar 06 '18 19:03 kurin