-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
fix(socket sink): gracefully shutdown on reload when stream is terminated #21455
fix(socket sink): gracefully shutdown on reload when stream is terminated #21455
Conversation
5ba54b2
to
76070ce
Compare
76070ce
to
a449052
Compare
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.
Great fix 👍
Regression Detector ResultsRun ID: a2138e42-06b3-41c8-b7eb-52311561cb98 Metrics dashboard Baseline: 5581b24 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | file_to_blackhole | egress throughput | -4.25 | [-11.15, +2.66] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | splunk_hec_route_s3 | ingress throughput | +3.67 | [+3.35, +3.99] | |
➖ | http_to_http_acks | ingress throughput | +2.97 | [+1.74, +4.20] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +2.06 | [+1.95, +2.16] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | +1.14 | [+1.02, +1.26] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +0.95 | [+0.76, +1.13] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.77 | [+0.67, +0.87] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.57 | [+0.44, +0.69] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +0.54 | [+0.45, +0.63] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +0.50 | [+0.40, +0.60] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.17 | [+0.07, +0.27] | |
➖ | http_to_http_noack | ingress throughput | +0.12 | [+0.05, +0.19] | |
➖ | http_to_http_json | ingress throughput | +0.08 | [+0.01, +0.14] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | +0.03 | [-0.04, +0.10] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.01 | [-0.09, +0.11] | |
➖ | fluent_elasticsearch | ingress throughput | +0.00 | [-0.49, +0.50] | |
➖ | syslog_loki | ingress throughput | -0.01 | [-0.08, +0.06] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.05 | [-0.14, +0.04] | |
➖ | http_to_s3 | ingress throughput | -0.19 | [-0.46, +0.08] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -0.80 | [-1.00, -0.59] | |
➖ | http_elasticsearch | ingress throughput | -1.03 | [-1.21, -0.86] | |
➖ | syslog_humio_logs | ingress throughput | -1.27 | [-1.40, -1.14] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -1.58 | [-1.69, -1.47] | |
➖ | http_text_to_http_json | ingress throughput | -2.24 | [-2.34, -2.14] | |
➖ | socket_to_socket_blackhole | ingress throughput | -2.38 | [-2.44, -2.31] | |
➖ | otlp_http_to_blackhole | ingress throughput | -3.03 | [-3.16, -2.91] | |
➖ | file_to_blackhole | egress throughput | -4.25 | [-11.15, +2.66] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
Regression Detector ResultsRun ID: 32419d32-3e15-4f6d-8ba9-0c0341b2926a Metrics dashboard Baseline: 290b9dd Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | file_to_blackhole | egress throughput | -1.50 | [-8.65, +5.66] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | http_to_http_acks | ingress throughput | +2.45 | [+1.21, +3.69] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +1.98 | [+1.89, +2.06] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | +1.34 | [+1.14, +1.55] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +0.97 | [+0.84, +1.10] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | +0.76 | [+0.65, +0.88] | |
➖ | fluent_elasticsearch | ingress throughput | +0.70 | [+0.20, +1.20] | |
➖ | syslog_loki | ingress throughput | +0.66 | [+0.59, +0.73] | |
➖ | otlp_http_to_blackhole | ingress throughput | +0.53 | [+0.41, +0.65] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | +0.29 | [+0.17, +0.41] | |
➖ | socket_to_socket_blackhole | ingress throughput | +0.21 | [+0.15, +0.27] | |
➖ | http_to_http_noack | ingress throughput | +0.18 | [+0.09, +0.27] | |
➖ | http_to_http_json | ingress throughput | +0.13 | [+0.04, +0.22] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +0.08 | [-0.02, +0.19] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | +0.02 | [-0.08, +0.12] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | +0.01 | [-0.08, +0.10] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | -0.00 | [-0.10, +0.10] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.01 | [-0.09, +0.08] | |
➖ | http_text_to_http_json | ingress throughput | -0.18 | [-0.31, -0.06] | |
➖ | http_to_s3 | ingress throughput | -0.26 | [-0.53, +0.02] | |
➖ | syslog_humio_logs | ingress throughput | -0.59 | [-0.71, -0.47] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.79 | [-0.90, -0.67] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -1.31 | [-1.51, -1.12] | |
➖ | file_to_blackhole | egress throughput | -1.50 | [-8.65, +5.66] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -1.74 | [-1.84, -1.63] | |
➖ | splunk_hec_route_s3 | ingress throughput | -1.79 | [-2.10, -1.48] | |
➖ | http_elasticsearch | ingress throughput | -2.81 | [-2.96, -2.67] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
Regression Detector ResultsRun ID: 55fb6e0a-d9d5-483d-8d5b-02a3d848167e Metrics dashboard Baseline: 775d9de Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | file_to_blackhole | egress throughput | +23.30 | [+15.53, +31.06] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
✅ | file_to_blackhole | egress throughput | +23.30 | [+15.53, +31.06] | |
➖ | syslog_humio_logs | ingress throughput | +2.88 | [+2.73, +3.03] | |
➖ | syslog_splunk_hec_logs | ingress throughput | +2.58 | [+2.51, +2.65] | |
➖ | otlp_http_to_blackhole | ingress throughput | +2.40 | [+2.26, +2.53] | |
➖ | syslog_log2metric_humio_metrics | ingress throughput | +2.35 | [+2.20, +2.50] | |
➖ | syslog_log2metric_tag_cardinality_limit_blackhole | ingress throughput | +1.85 | [+1.75, +1.94] | |
➖ | splunk_hec_route_s3 | ingress throughput | +1.49 | [+1.19, +1.80] | |
➖ | http_to_http_acks | ingress throughput | +1.11 | [-0.13, +2.34] | |
➖ | http_text_to_http_json | ingress throughput | +0.83 | [+0.71, +0.96] | |
➖ | syslog_loki | ingress throughput | +0.65 | [+0.55, +0.75] | |
➖ | http_to_s3 | ingress throughput | +0.04 | [-0.24, +0.33] | |
➖ | http_to_http_json | ingress throughput | +0.02 | [-0.01, +0.05] | |
➖ | splunk_hec_to_splunk_hec_logs_acks | ingress throughput | +0.00 | [-0.10, +0.11] | |
➖ | http_to_http_noack | ingress throughput | +0.00 | [-0.02, +0.02] | |
➖ | splunk_hec_to_splunk_hec_logs_noack | ingress throughput | -0.00 | [-0.10, +0.10] | |
➖ | splunk_hec_indexer_ack_blackhole | ingress throughput | -0.00 | [-0.08, +0.07] | |
➖ | socket_to_socket_blackhole | ingress throughput | -0.19 | [-0.26, -0.11] | |
➖ | datadog_agent_remap_blackhole | ingress throughput | -0.63 | [-0.74, -0.51] | |
➖ | syslog_log2metric_splunk_hec_metrics | ingress throughput | -0.67 | [-0.80, -0.53] | |
➖ | otlp_grpc_to_blackhole | ingress throughput | -0.67 | [-0.79, -0.55] | |
➖ | datadog_agent_remap_blackhole_acks | ingress throughput | -1.00 | [-1.11, -0.90] | |
➖ | syslog_regex_logs2metric_ddmetrics | ingress throughput | -1.29 | [-1.41, -1.16] | |
➖ | fluent_elasticsearch | ingress throughput | -1.38 | [-1.87, -0.89] | |
➖ | datadog_agent_remap_datadog_logs_acks | ingress throughput | -2.13 | [-2.31, -1.95] | |
➖ | datadog_agent_remap_datadog_logs | ingress throughput | -2.47 | [-2.69, -2.25] | |
➖ | http_elasticsearch | ingress throughput | -3.09 | [-3.31, -2.88] |
Explanation
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
fixes: #15952
fixes: #14515
It looks like a PR introduced a regression while making changes to the tcp socket sink to emit internal telemetry in accordance with the component specification.
This introduced a bug where the
TcpSink
crashes Vector during config reloads, while events are flowing through the topology.The fix is to restore the behavior of peeking onto the stream before attempting to access the next event.
To test this, just use the
socket
sink intcp
mode, and watch the vector config. Send events continuously. Change the name of the input to the sink. In the before case, it crashes. After the fix, it does not.reproducing it (before fix)
after the fix: