-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new tools for http.Handler instrumentation #224
Comments
https://blog.golang.org/http-tracing and https://github.com/davecheney/httpstat might be useful to look at. |
Hi. I need this, is anyone else working on it? If not, I'll try to work on it. |
@stuartnelson3 is, kind of. And it already became apparent how hard this is to get right and how much context is needed. Not sure if it makes any sense at this time to involve somebody who misses that context. |
@beorn7 Sure, I understand. @stuartnelson3 Is this context to read somewhere? Is the current work available somewhere? Edit: I see you both work at SoundCloud so I guess it was chatted about? |
That is correct, context was shared with me face-to-face. I'll try to look at this soon, but as is recommended in the library, rolling your own custom handler, at this point, will probably be a much quicker solution. |
Just for others (following comment in: https://github.com/prometheus/client_golang/blob/master/prometheus/http.go#L152):
The links provided by by @beorn7 are about the client tracing and required to modify the You can find my instrumented handler at: https://github.com/orian/go-http-instrument |
As mentioned in the doc comment,
InstrumentHandler
has issues beyond repair.In the promhttp package, new utilities should be provided to instrument handlers and round-trippers in a more specific way.
See #200, #101, #57 for other issues to solve on the way.
The text was updated successfully, but these errors were encountered: