agent status shows Pipeline Latency as time.Duration

[keisku]

What does this PR do?

agent status shows Pipeline Latency as time.Duration.

Motivation

Before this PR, agent status shows 0 when latency is less than 1 ms. It makes us confused.

Describe how you validated your changes

docker run --name datadog-agent -d --cgroupns host --pid host \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
-v /proc/:/host/proc/:ro -v /sys/fs/cgroup/:/host/sys/fs/cgroup:ro \
-e DD_API_KEY=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx \
-e DD_LOGS_ENABLED=true \
$(docker build -t datadog-agent --quiet -<<-EOD
FROM datadog/agent-dev:keisku-stats-tracker-py3
COPY --chmod=755 <<conf.yaml /etc/datadog-agent/conf.d/file-logger.d/
logs:
  - type: file
    path: /var/log/file-logger/file.log
    service: file-logger
    source: python
conf.yaml
COPY --chmod=755 <<file.log /var/log/file-logger/
file.log
COPY --chmod=755 <<file-logger.py /opt/datadog-agent/scripts/
import os
import time

log_file_path = "/var/log/file-logger/file.log"
text = """hello
"""

while True:
    with open(log_file_path, "a") as f:
        f.write(text)
    time.sleep(5)
file-logger.py
EOD
)

docker exec -it datadog-agent /opt/datadog-agent/embedded/bin/python /opt/datadog-agent/scripts/file-logger.py

docker exec -it datadog-agent agent status
....
==========
Logs Agent
==========

    Reliable: Sending compressed logs in HTTPS to agent-http-intake.logs.datadoghq.com on port 443
    BytesSent: 789625
    EncodedBytesSent: 109832
    LogsProcessed: 3
    LogsSent: 12
    RetryCount: 0
    RetryTimeSpent: 0s
    CoreAgentProcessOpenFiles: 39
    OSFileLimit: 1048576
  ============
  Integrations
  ============

  file-logger
  -----------
    - Type: file
      Path: /var/log/file-logger/file.log
      Service: file-logger
      Source: python
      Status: OK
      Inputs:
        /var/log/file-logger/file.log  
      Bytes Read: 18   
      Pipeline Latency:
        Average Latency: 73.5µs
        24h Average Latency: 73.5µs
        Peak Latency: 105.358µs
        24h Peak Latency: 105.358µs

Possible Drawbacks / Trade-offs

Additional Notes

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor 701ea4a893ea0f2fd137f9ac0efad01ce158f55f

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.03MB	⚠️	1190.80MB	1190.77MB	140.00MB
datadog-agent-x86_64-rpm	0.03MB	⚠️	1200.09MB	1200.07MB	140.00MB
datadog-agent-x86_64-suse	0.03MB	⚠️	1200.09MB	1200.07MB	140.00MB
datadog-iot-agent-x86_64-rpm	0.00MB	✅	113.42MB	113.42MB	10.00MB
datadog-iot-agent-x86_64-suse	0.00MB	✅	113.42MB	113.42MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.77MB	55.77MB	10.00MB
datadog-heroku-agent-amd64-deb	0.00MB	✅	505.21MB	505.21MB	70.00MB
datadog-iot-agent-amd64-deb	0.00MB	✅	113.35MB	113.35MB	10.00MB
datadog-iot-agent-arm64-deb	0.00MB	✅	108.81MB	108.81MB	10.00MB
datadog-dogstatsd-x86_64-rpm	-0.00MB	✅	78.64MB	78.65MB	10.00MB
datadog-dogstatsd-x86_64-suse	-0.00MB	✅	78.64MB	78.65MB	10.00MB
datadog-iot-agent-aarch64-rpm	-0.00MB	✅	108.88MB	108.88MB	10.00MB
datadog-dogstatsd-amd64-deb	-0.00MB	✅	78.57MB	78.57MB	10.00MB
datadog-agent-aarch64-rpm	-0.01MB	✅	944.36MB	944.37MB	140.00MB
datadog-agent-arm64-deb	-0.01MB	✅	935.09MB	935.10MB	140.00MB

Decision

⚠️ Warning

[agent-platform-auto-pr]

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=51802351 --os-family=ubuntu

Note: This applies to commit bc18fbe

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: e8038791-e828-41b9-9d9f-55e3bf482b4d

Baseline: 701ea4a
Comparison: bc18fbe
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+1.27	[+0.58, +1.95]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	+0.43	[-0.04, +0.90]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.40	[-2.85, +3.64]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.32	[-0.47, +1.12]	1	Logs
➖	quality_gate_idle	memory utilization	+0.17	[+0.13, +0.21]	1	Logs bounds checks dashboard
➖	file_to_blackhole_500ms_latency	egress throughput	+0.16	[-0.62, +0.93]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.13	[-0.51, +0.77]	1	Logs
➖	file_tree	memory utilization	+0.10	[-0.04, +0.23]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	+0.07	[-0.81, +0.94]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	+0.04	[-0.90, +0.98]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.02	[-0.68, +0.72]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.12, +0.11]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.03	[-0.92, +0.86]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.59	[-0.67, -0.51]	1	Logs bounds checks dashboard
➖	tcp_syslog_to_blackhole	ingress throughput	-1.61	[-1.66, -1.55]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	file_to_blackhole_300ms_latency	lost_bytes	9/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	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	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	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_logs, bounds check memory_usage: 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_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[keisku]

/merge

[dd-devflow]

Devflow running: /merge

View all feedbacks in Devflow UI.

---

2024-12-27 10:18:10 UTC ℹ️ MergeQueue: pull request added to the queue

The median merge time in main is 35m.

---

2024-12-27 10:52:18 UTC ℹ️ MergeQueue: This merge request was merged