-
Notifications
You must be signed in to change notification settings - Fork 1.8k
fix(datadog_agent source): Silence the "Source send cancelled." error #23097
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR silences the "Source send cancelled." error and its corresponding metric for the datadog_agent source by disabling the unsent event counting behavior.
- Updated datadog_agent source to call silence_unsent_events() on the SourceSender.
- Refactored UnsentEventCount in SourceSender to optionally count events using an Option.
- Added a changelog fragment to document the change.
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
File | Description |
---|---|
src/sources/datadog_agent/mod.rs | Modified the warp filter builder to mute the unsent event count error by silencing events. |
src/source_sender/mod.rs | Added silence_unsent_events() and refactored UnsentEventCount to optionally disable counting. |
changelog.d/fix-datadog-agent-source-sender-warning.fix.md | Provided a changelog entry summarizing the fix. |
5ad705c
to
e64b9bc
Compare
Datadog ReportBranch report: ❌ 1 Failed (1 Known Flaky), 7 Passed, 0 Skipped, 25.47s Total Time ❌ Failed Tests (1)
|
This is reliably breaking the |
Hello, I'm not sure if you're taking feedback on this PR, but my team uses Vector extensively and we find this error and associated metric very useful. "Source send cancelled" due to a timeout can mean that Vector is saturated and/or that a component is applying backpressure. "Source send cancelled" can be a symptom of various capacity issues including (but not limited to) saturated sink buffers, undersized compute, or even just general slowness on whatever's on the other side of the sink (e2e acknowledgements affect some but not all of these). If possible, we'd like to keep these metrics and log events. They act as an early warning sign for us because even though the Datadog Agent will retransmit, an increase in "Source send cancelled" errors means that we are beginning to erode our safety margin. |
Summary
Eliminated the "Source send cancelled." error and corresponding metric for the
datadog_agent
source, as Datadog Agent will always resend events when the connection is dropped after a timeout.Change Type
Is this a breaking change?
How did you test this PR?
Does this PR include user facing changes?
Notes
@vectordotdev/vector
to reach out to us regarding this PR.pre-push
hook, please see this template.cargo fmt --all
cargo clippy --workspace --all-targets -- -D warnings
cargo nextest run --workspace
(alternatively, you can runcargo test --all
)./scripts/check_changelog_fragments.sh
git merge origin master
andgit push
.Cargo.lock
), pleaserun
cargo vdev build licenses
to regenerate the license inventory and commit the changes (if any). More details here.