chore(deps): update integrations-core digest to 0fb7148#47966
chore(deps): update integrations-core digest to 0fb7148#47966renovate[bot] wants to merge 1 commit intomainfrom
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4f81416f4c
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
release.json
Outdated
| "AGENT_DATA_PLANE_HASH_LINUX_ARM64": "d3bc10e2a2f136fc4c7f5f5a4484088aff8e9fd26001c7c6aa9e6f8665856137", | ||
| "AGENT_DATA_PLANE_VERSION": "0.1.34", | ||
| "INTEGRATIONS_CORE_VERSION": "2d9b8f766a47fd8101886a19c29229f86968519a", | ||
| "INTEGRATIONS_CORE_VERSION": "acbcd4a4a9ac5ca129a8218e3221cdbb8b79d870", |
There was a problem hiding this comment.
Stop caching failed Kafka metadata fetches as fresh
Bumping INTEGRATIONS_CORE_VERSION to 99c4705 pulls in a regression in kafka_consumer/datadog_checks/kafka_consumer/cluster_metadata.py: _collect_broker_metadata, _collect_topic_metadata, and _collect_schema_registry_info now call _mark_items_fetched(...) with the entire batch (broker_ids_batch, topic_names_to_fetch, subjects_to_check) even when individual describe_configs/Schema Registry calls failed. In the previous implementation (2a97cf5), only the successfully fetched keys were marked fresh. With enable_cluster_monitoring enabled, any transient Admin API or Schema Registry error now suppresses retries for the full refresh interval, so broker/topic config metrics and schema events can stay stale for minutes after a brief outage.
Useful? React with 👍 / 👎.
Files inventory check summaryFile checks results against ancestor 178cf93a: Results for datadog-agent_7.78.0~devel.git.756.077ebef.pipeline.103663971-1_amd64.deb:Detected file changes:
|
Static quality checks❌ Please find below the results from static quality gates Error
Gate failure full details
Static quality gates prevent the PR to merge! Successful checksInfo
15 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 178cf93 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | -2.82 | [-5.79, +0.14] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_memory | memory utilization | +1.04 | [+0.90, +1.18] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.91 | [+0.67, +1.15] | 1 | Logs bounds checks dashboard |
| ➖ | quality_gate_logs | % cpu utilization | +0.91 | [-0.60, +2.42] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.31 | [+0.15, +0.46] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.30 | [+0.24, +0.35] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.14 | [+0.08, +0.20] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.07 | [-0.32, +0.46] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.04 | [+0.00, +0.07] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.04 | [-0.38, +0.46] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.08, +0.09] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.01 | [-0.17, +0.18] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.49, +0.50] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.00 | [-0.05, +0.06] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.10, +0.11] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.00 | [-0.20, +0.20] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.20, +0.20] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.09 | [-0.27, +0.10] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.14 | [-0.20, -0.08] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.47 | [-0.61, -0.33] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.56 | [-0.78, -0.33] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.61 | [-0.71, -0.51] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -2.03 | [-2.16, -1.89] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | -2.82 | [-5.79, +0.14] | 1 | Logs |
Bounds Checks: ❌ Failed
| perf | experiment | bounds_check_name | replicates_passed | observed_value | links |
|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | 741 ≥ 26 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | 274.18MiB ≤ 370MiB | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | 720 ≥ 26 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | 0.19GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_0ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | 0.23GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_1000ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | 0.19GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_100ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | 0.21GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_500ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | 3 = 3 | bounds checks dashboard |
| ❌ | quality_gate_idle | memory_usage | 9/10 | 175.80MiB > 175MiB | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | 2 ≤ 3 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | 488.24MiB ≤ 550MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | 4 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | 205.45MiB ≤ 220MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | 349.78 ≤ 2000 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | 405.26MiB ≤ 475MiB | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | missed_bytes | 10/10 | 0B = 0B | 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
❌ Failed. Some Quality Gates were violated.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_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 missed_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: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
This PR is rejected because it was updated |
4f81416 to
0dc4c00
Compare
0dc4c00 to
1e7ea28
Compare
1e7ea28 to
92982b2
Compare
92982b2 to
fafd3e1
Compare
|
/merge |
|
View all feedbacks in Devflow UI.
This pull request is not mergeable according to GitHub. Common reasons include pending required checks, missing approvals, or merge conflicts — but it could also be blocked by other repository rules or settings.
devflow unqueued this merge request: It did not become mergeable within the expected time |
2fd505c to
266d582
Compare
266d582 to
426df2d
Compare
426df2d to
fcc21bd
Compare
fcc21bd to
003f23e
Compare
003f23e to
4c618bd
Compare
4c618bd to
65d8045
Compare
65d8045 to
573dadb
Compare
573dadb to
b368f46
Compare
b368f46 to
7d7658f
Compare
7d7658f to
d910b88
Compare
d910b88 to
077ebef
Compare
077ebef to
b204658
Compare
This PR contains the following updates:
2d9b8f7→0fb7148Configuration
📅 Schedule: Branch creation - Between 02:00 AM and 06:59 AM, only on Monday and Wednesday ( * 2-6 * * 1,3 ) (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.