Skip to content
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

Metric events for Request content source error and request write failure #251

Closed
NiteshKant opened this issue Oct 22, 2014 · 0 comments
Closed
Assignees
Milestone

Comments

@NiteshKant
Copy link
Member

The following two metrics will give insight into HttpClientRequest write failures:

  • How many times HttpClientRequest content observable returned an error.
  • How many times the write of HttpClientRequest on the channel failed. Currently, there is a metric on how many times writing of header failed and how many times writing of content failed. Since, these metrics are over all requests, there is no way to determine how many request writes failed.
@NiteshKant NiteshKant self-assigned this Oct 22, 2014
@NiteshKant NiteshKant added this to the 0.3.15 milestone Oct 22, 2014
NiteshKant pushed a commit to NiteshKant/RxNetty that referenced this issue Oct 22, 2014
ReactiveX#248 (Connection close cancels pending writes): Now only cancelling when a pooled connection is returned to the pool.
ReactiveX#249 (`BytesInspector` does not record events for `ByteBufHolder` and `FileRegion`): Recording events for ByteBufHolder and FileRegion
ReactiveX#250 (Connection closing and content stream behavior): Send error on content stream if the request/response is not completed on server/client.
ReactiveX#251 (Metric events for Request content source error and request write failure): Added metrics
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant