You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Problem
If warp stops driving a request, we don't increment component_discarded_events_total. This results in a discrepancy for events in / events out for the source. This has been observed in the Datadog Agent source in particular.
This can occur when the client has a request timeout shorter than the time it takes Vector to process the request.
dsmith3197
changed the title
HTTP-Based Sources doesn't increment component_discarded_events_total when requests are dropped
HTTP-Based Sources don't increment component_discarded_events_total when requests are dropped
Sep 22, 2023
A note for the community
Problem
If warp stops driving a request, we don't increment
component_discarded_events_total
. This results in a discrepancy for events in / events out for the source. This has been observed in the Datadog Agent source in particular.This can occur when the client has a request timeout shorter than the time it takes Vector to process the request.
Configuration
No response
Version
0.32.2
Debug Output
No response
Example Data
No response
Additional Context
No response
References
#17006
The text was updated successfully, but these errors were encountered: