-
Notifications
You must be signed in to change notification settings - Fork 1.3k
feat: added truncatedLogs metric #37703
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
Conversation
9fdc953
to
d6abe10
Compare
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 9d6ecd4 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.49 | [+0.44, +0.54] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.36 | [-0.51, +1.24] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.20 | [-2.55, +2.96] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle_all_features | memory utilization | +0.12 | [+0.04, +0.21] | 1 | Logs bounds checks dashboard |
➖ | ddot_logs | memory utilization | +0.12 | [-0.02, +0.26] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.08 | [-0.46, +0.63] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.08 | [-0.15, +0.31] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.08 | [+0.02, +0.13] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | +0.03 | [-0.07, +0.13] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.02 | [-0.15, +0.18] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.27, +0.27] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.01 | [-0.62, +0.61] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.61, +0.57] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.06 | [-0.65, +0.54] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.07 | [-0.65, +0.51] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.08 | [-0.63, +0.48] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.72, +0.56] | 1 | Logs |
➖ | file_tree | memory utilization | -0.24 | [-0.36, -0.11] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.29 | [-0.41, -0.16] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.44 | [-0.56, -0.33] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.21 | [-1.28, -1.14] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -1.54 | [-4.47, +1.38] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
✅ | docker_containers_memory | simple_check_run | 10/10 | |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
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".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
3ba6eef
to
9c992a2
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.
Nice work!
releasenotes/notes/truncated_count_metric-ef102f7deabb9206.yaml
Outdated
Show resolved
Hide resolved
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
lucas.tembras@datadoghq.com unqueued this merge request |
/remove |
View all feedbacks in Devflow UI.
|
Co-authored-by: Jesse Szwedko <jesse.szwedko@datadoghq.com>
5ee5fac
to
75c4605
Compare
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
datadog.agent.logs.truncated
metric inmetrics.go
single_line_handler.go
,multiline_handler.go
, andaggregator.go
to increment ourlogs.truncated
metric by 1 while also implementing safeguards to check whether the message or message origin is nil to successfully increment the count with the message origin service and source.status_test.go
andmetrics_test.go
to include and check for new metric.LogsTruncated
tobuilder.go
to expose new metricMotivation
This metric enables customers to monitor the number of logs truncated by the Agent. It addresses the customer feature request FRLOGSS-3606 and aligns with the internal telemetry initiative AGNTLOG-227. The metric name differs from the backend’s datadog.estimated_usage.logs.truncated_count to maintain consistency with existing Agent metric naming conventions.
Describe how you validated your changes
Ran
curl http://localhost:5000/telemetry | grep "truncated"
to verify existence of metric on local DataDog agent.Also, modified unit tests and ran them to ensure expected behavior.
Possible Drawbacks / Trade-offs
Additional Notes