Skip to content
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

[HA Agent] Add datadog.agent.ha_agent.integration_runs #33233

Merged
merged 31 commits into from
Feb 3, 2025

Conversation

AlexandreYang
Copy link
Member

@AlexandreYang AlexandreYang commented Jan 22, 2025

What does this PR do?

[HA Agent] Add datadog.agent.ha_agent.integration_runs

Motivation

datadog.agent.ha_agent.integration_runs for HA Agent feature OOTB dashboard, see example below.

It helps know which agent is running which integrations over time.

image

Describe how you validated your changes

Possible Drawbacks / Trade-offs

Additional Notes

@github-actions github-actions bot added medium review PR review might take time team/ndm-core labels Jan 22, 2025
@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Jan 22, 2025

Uncompressed package size comparison

Comparison with ancestor afb45257bea753d2e534ec9584bc1a3afe3fdee5

Diff per package
package diff status size ancestor threshold
datadog-iot-agent-x86_64-rpm 0.01MB ⚠️ 93.91MB 93.90MB 0.50MB
datadog-iot-agent-x86_64-suse 0.01MB ⚠️ 93.91MB 93.90MB 0.50MB
datadog-iot-agent-amd64-deb 0.01MB ⚠️ 93.84MB 93.84MB 0.50MB
datadog-iot-agent-arm64-deb 0.01MB ⚠️ 89.89MB 89.89MB 0.50MB
datadog-iot-agent-aarch64-rpm 0.00MB 89.96MB 89.96MB 0.50MB
datadog-agent-amd64-deb 0.00MB 877.19MB 877.18MB 0.50MB
datadog-agent-x86_64-rpm 0.00MB 886.93MB 886.92MB 0.50MB
datadog-agent-x86_64-suse 0.00MB 886.93MB 886.92MB 0.50MB
datadog-agent-arm64-deb 0.00MB 864.97MB 864.97MB 0.50MB
datadog-agent-aarch64-rpm 0.00MB 874.69MB 874.69MB 0.50MB
datadog-heroku-agent-amd64-deb 0.00MB 456.45MB 456.45MB 0.50MB
datadog-dogstatsd-amd64-deb 0.00MB 59.02MB 59.02MB 0.50MB
datadog-dogstatsd-x86_64-rpm 0.00MB 59.10MB 59.10MB 0.50MB
datadog-dogstatsd-x86_64-suse 0.00MB 59.10MB 59.10MB 0.50MB
datadog-dogstatsd-arm64-deb 0.00MB 56.51MB 56.51MB 0.50MB

Decision

⚠️ Warning

@agent-platform-auto-pr
Copy link
Contributor

agent-platform-auto-pr bot commented Jan 22, 2025

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=54653946 --os-family=ubuntu

Note: This applies to commit b5001c3

Copy link

cit-pr-commenter bot commented Jan 22, 2025

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: d419b0e5-5edd-4ab8-bd47-38b43ec68b99

Baseline: afb4525
Comparison: b5001c3
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf experiment goal Δ mean % Δ mean % CI trials links
quality_gate_idle memory utilization +0.47 [+0.43, +0.52] 1 Logs bounds checks dashboard
file_to_blackhole_1000ms_latency_linear_load egress throughput +0.17 [-0.30, +0.64] 1 Logs
file_to_blackhole_500ms_latency egress throughput +0.08 [-0.70, +0.86] 1 Logs
file_to_blackhole_1000ms_latency egress throughput +0.04 [-0.74, +0.83] 1 Logs
file_to_blackhole_0ms_latency_http1 egress throughput +0.03 [-0.85, +0.90] 1 Logs
file_to_blackhole_0ms_latency_http2 egress throughput +0.02 [-0.82, +0.87] 1 Logs
uds_dogstatsd_to_api ingress throughput +0.00 [-0.28, +0.28] 1 Logs
quality_gate_idle_all_features memory utilization +0.00 [-0.06, +0.07] 1 Logs bounds checks dashboard
tcp_dd_logs_filter_exclude ingress throughput +0.00 [-0.02, +0.02] 1 Logs
file_to_blackhole_300ms_latency egress throughput -0.00 [-0.63, +0.63] 1 Logs
file_to_blackhole_0ms_latency egress throughput -0.01 [-0.90, +0.88] 1 Logs
tcp_syslog_to_blackhole ingress throughput -0.06 [-0.13, +0.01] 1 Logs
file_to_blackhole_100ms_latency egress throughput -0.06 [-0.74, +0.62] 1 Logs
file_tree memory utilization -0.30 [-0.37, -0.23] 1 Logs
quality_gate_logs % cpu utilization -1.25 [-4.26, +1.76] 1 Logs
uds_dogstatsd_to_api_cpu % cpu utilization -1.45 [-2.31, -0.58] 1 Logs

Bounds Checks: ✅ Passed

perf experiment bounds_check_name replicates_passed links
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
quality_gate_logs lost_bytes 10/10
quality_gate_logs memory_usage 10/10

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:

  1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

  2. 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.

  3. 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 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_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
  • quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.

Comment on lines 208 to 213
senderShouldCommit = true
}
if senderShouldCommit {
Copy link
Member Author

@AlexandreYang AlexandreYang Jan 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note for reviewers: Using senderShouldCommit bool helps avoid sender.Commit() twice around line 208 and 164.

@AlexandreYang AlexandreYang changed the title [HA Agent] draft integration metrics [HA Agent] Add datadog.agent.ha_agent.integration_runs Jan 23, 2025
@AlexandreYang AlexandreYang changed the base branch from main to NDMII-3313-datadog-agent-ha-agent-running January 23, 2025 09:09
@AlexandreYang AlexandreYang changed the base branch from NDMII-3313-datadog-agent-ha-agent-running to main January 23, 2025 09:09
@AlexandreYang AlexandreYang changed the base branch from main to NDMII-3313-datadog-agent-ha-agent-running January 23, 2025 09:11
@AlexandreYang AlexandreYang changed the base branch from NDMII-3313-datadog-agent-ha-agent-running to main January 23, 2025 09:11
@AlexandreYang AlexandreYang force-pushed the NDMII-3313-integration-metric branch 2 times, most recently from af5e6f0 to ae78648 Compare January 23, 2025 09:23
@AlexandreYang AlexandreYang force-pushed the NDMII-3313-integration-metric branch from ae78648 to a1e484a Compare January 23, 2025 09:26
@AlexandreYang AlexandreYang changed the base branch from main to NDMII-3313-datadog-agent-ha-agent-running January 23, 2025 09:26
@AlexandreYang AlexandreYang marked this pull request as ready for review January 23, 2025 09:28
@AlexandreYang AlexandreYang requested a review from a team as a code owner January 23, 2025 09:28
@AlexandreYang AlexandreYang requested review from a team as code owners February 1, 2025 16:27
@AlexandreYang AlexandreYang removed request for a team February 1, 2025 16:29
Base automatically changed from NDMII-3313-datadog-agent-ha-agent-running to main February 1, 2025 19:06
@AlexandreYang AlexandreYang added changelog/no-changelog qa/done QA done before merge and regressions are covered by tests team/ndm-core and removed changelog/no-changelog qa/done QA done before merge and regressions are covered by tests team/ndm-core labels Feb 1, 2025
@AlexandreYang
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Feb 1, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-02-01 20:47:17 UTC ℹ️ MergeQueue: waiting for PR to be ready

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.
Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.


2025-02-01 20:50:24 UTC ⚠️ MergeQueue: This merge request was unqueued

[email protected] unqueued this merge request

@AlexandreYang
Copy link
Member Author

/remove

@dd-devflow
Copy link

dd-devflow bot commented Feb 1, 2025

Devflow running: /remove

View all feedbacks in Devflow UI.


2025-02-01 20:50:23 UTC ℹ️ Devflow: /remove

@AlexandreYang
Copy link
Member Author

/remove

@dd-devflow
Copy link

dd-devflow bot commented Feb 1, 2025

Devflow running: /remove

View all feedbacks in Devflow UI.


2025-02-01 21:05:31 UTCDevflow: /remove

This merge request is not in the queue and can't be unqueued

To get help about command usage, write /remove --help

If you need support, contact us on Slack #devflow with those details!

@AlexandreYang AlexandreYang requested review from a team and hush-hush February 1, 2025 21:10
Copy link
Member

@hush-hush hush-hush left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added a quick question but look good overall for agent-configuration.

@@ -249,6 +257,9 @@ func (cs *Stats) Add(t time.Duration, err error, warnings []error, metricStats S
cs.TotalEventPlatformEvents[k] = cs.TotalEventPlatformEvents[k] + v
cs.EventPlatformEvents[k] = v
}
if haagent != nil && haagent.Enabled() && haagent.IsHaIntegration(cs.CheckName) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we could include the haagent.Enabled() check in IsHaIntegration to simplify usage ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum, I think it's not ideal since they mean different things. Can be misleading to have haagent.Enabled() check in IsHaIntegration() since a check can be flagged as HA, but HA Agent feature can be disabled.

@github-actions github-actions bot added long review PR is complex, plan time to review it and removed medium review PR review might take time labels Feb 3, 2025
@AlexandreYang
Copy link
Member Author

/merge

@dd-devflow
Copy link

dd-devflow bot commented Feb 3, 2025

Devflow running: /merge

View all feedbacks in Devflow UI.


2025-02-03 14:53:45 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 27m.


2025-02-03 15:28:38 UTC ℹ️ MergeQueue: Readding this merge request to the queue because another merge request processed with yours failed. No action is needed from your side.


2025-02-03 16:00:33 UTC ℹ️ MergeQueue: This merge request was merged

@dd-mergequeue dd-mergequeue bot merged commit a85f505 into main Feb 3, 2025
231 checks passed
@dd-mergequeue dd-mergequeue bot deleted the NDMII-3313-integration-metric branch February 3, 2025 16:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog/no-changelog long review PR is complex, plan time to review it qa/done QA done before merge and regressions are covered by tests team/ndm-core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants