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

Updating Default Rate Limit Value and Usage Based on Sample Rate #2912

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

link04
Copy link
Contributor

@link04 link04 commented Oct 25, 2024

Description

Updating the default value for the DD_TRACE_RATE_LIMIT from 0 to 100 to match RFC and most of all other languages and also only make use of the config when DD_TRACE_SAMPLE_RATE is set.

Related Jira: https://datadoghq.atlassian.net/browse/APMAPI-496

Reviewer checklist

  • Test coverage seems ok.
  • Appropriate labels assigned.

@codecov-commenter
Copy link

codecov-commenter commented Oct 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.38%. Comparing base (e314256) to head (92dac2b).

Additional details and impacted files

Impacted file tree graph

@@              Coverage Diff              @@
##             master    #2912       +/-   ##
=============================================
+ Coverage     51.81%   72.38%   +20.56%     
  Complexity     2526     2526               
=============================================
  Files           135      135               
  Lines         14400    14400               
  Branches        989      989               
=============================================
+ Hits           7462    10424     +2962     
+ Misses         6393     3433     -2960     
+ Partials        545      543        -2     
Flag Coverage Δ
appsec-extension 68.34% <ø> (+0.17%) ⬆️
tracer-php 73.96% <ø> (+28.52%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 37 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e314256...92dac2b. Read the comment docs.

@pr-commenter
Copy link

pr-commenter bot commented Oct 25, 2024

Benchmarks [ tracer ]

Benchmark execution time: 2024-11-05 19:47:29

Comparing candidate commit 92dac2b in PR branch maximo/consistent-config-rate-limit with baseline commit e314256 in branch master.

Found 1 performance improvements and 1 performance regressions! Performance is the same for 176 metrics, 0 unstable metrics.

scenario:PDOBench/benchPDOBaseline-opcache

  • 🟥 execution_time [+3.581µs; +10.791µs] or [+2.002%; +6.034%]

scenario:SamplingRuleMatchingBench/benchRegexMatching3-opcache

  • 🟩 execution_time [-504.195ns; -199.205ns] or [-6.978%; -2.757%]

@link04 link04 marked this pull request as ready for review October 25, 2024 23:04
@link04 link04 requested a review from a team as a code owner October 25, 2024 23:04
@bwoebi bwoebi force-pushed the maximo/consistent-config-rate-limit branch from fe12510 to 92dac2b Compare November 5, 2024 19:20
@link04 link04 merged commit 5a693b6 into master Nov 5, 2024
718 of 743 checks passed
@link04 link04 deleted the maximo/consistent-config-rate-limit branch November 5, 2024 23:52
@github-actions github-actions bot added this to the 1.5.0 milestone Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants