-
Notifications
You must be signed in to change notification settings - Fork 11
Investigate forwarder config key: forwarder_requeue_buffer_size #1755
Copy link
Copy link
Open
Labels
area/configConfiguration.Configuration.effort/simpleInvolves trivial changes that should be fine so long as the code compiles and tests pass.Involves trivial changes that should be fine so long as the code compiles and tests pass.forwarder/datadogDatadog forwarder.Datadog forwarder.type/investigationA potential issue that requires further investigation to quantify and categorize.A potential issue that requires further investigation to quantify and categorize.
Metadata
Metadata
Assignees
Labels
area/configConfiguration.Configuration.effort/simpleInvolves trivial changes that should be fine so long as the code compiles and tests pass.Involves trivial changes that should be fine so long as the code compiles and tests pass.forwarder/datadogDatadog forwarder.Datadog forwarder.type/investigationA potential issue that requires further investigation to quantify and categorize.A potential issue that requires further investigation to quantify and categorize.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Problem
The
forwarder_requeue_buffer_sizeconfig key sets the in-memory requeue channel size (a third queue alongside the trackedforwarder_high_prio_buffer_sizeandforwarder_low_prio_buffer_size). Omitting this is inconsistent with tracking the other two.This issue was split from #1680.
What needs to happen
Determine whether ADP's forwarder reads an equivalent config, hardcodes the value, or lacks the concept entirely. If ADP has an equivalent, confirm the key name and default. If not, decide whether to implement it.