-
Notifications
You must be signed in to change notification settings - Fork 337
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
Telemetry support #383
Comments
Great question! I think we should do this inside hackney. I know that hackney uses
|
If we are not implementing this into httpoison this discussion should be in https://github.com/benoitc/hackney and could be closed. |
I would love telemetry support. Right now, I have a use case where I want to be notified after every request with all the request and response infos. |
What I have done now is a lib that I used on top of httpoison where I have added my telemetry metrics. |
Any further thoughts on this? It'd be nice to get Ideally, we'd follow the recommendations for emitting |
Just stopping by to say that I'm also interested - I agree that it would be useful to get it added in Hackney itself, but that doesn't preclude HTTPoison also adding it, so that we get it one way or the other. 😉 |
Hi there! 🙂 I'm working on an XML tool that leverages Thanks |
@3fernandez I think we wanna emit start/stop/failure events, like @binaryseed mentioned, sort of like: :telemetry.execute([:ecto, :repo, :init], %{system_time: System.system_time()}, %{repo: repo, opts: opts}) That example is from a Telemetry Ecto example, but in |
The upstream hackney ticket is still open, so I think this one is still unsolved too? |
I am closing long opened issues on my account to make some cleanup. |
I think it'd be great to track this feature request for httpoison, and track the upstream hackney ticket. Would I need to make my own ticket that is a dupe of this closed ticket be the ideal solution for you? |
Yes sure. |
Are you planning to add telemetry support to the library? I can help with a PR.
Maybe it should be added in hackney.
The text was updated successfully, but these errors were encountered: