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

tracer: fix configure(collect_metrics) argument #1066

Merged
merged 2 commits into from
Sep 23, 2019
Merged

Conversation

jd
Copy link
Contributor

@jd jd commented Sep 19, 2019

  • The current code does not allow to disable collect_metrics by passing False
    to it.
  • The recent change from 2c41f15 made the hack
    in test_runtime_metrics to change the FLUSH_INTERVAL a noop, making the test
    taking 20 seconds to complete.

This patch fixes both issues by allowing the collect_metrics arguments to be
a boolean or a float representing the interval in seconds to use to collect the
runtime metrics. This makes sure users can disabled runtime metrics at any
time, and fixes the test for running in a less than a second.

@jd jd requested a review from a team as a code owner September 19, 2019 13:48
ddtrace/tracer.py Outdated Show resolved Hide resolved
@jd jd force-pushed the fix-delay branch 2 times, most recently from 915179f to a53c0ca Compare September 20, 2019 07:45
- The current code does not allow to disable collect_metrics by passing `False`
  to it.
- The recent change from 2c41f15 made the hack
  in test_runtime_metrics to change the FLUSH_INTERVAL a noop, making the test
  taking 20 seconds to complete.

This patch fixes both issues by allowing the `collect_metrics` arguments to be
a boolean or a float representing the interval in seconds to use to collect the
runtime metrics. This makes sure users can disabled runtime metrics at any
time, and fixes the test for running in a less than a second.
@jd jd merged commit 40ca95d into DataDog:master Sep 23, 2019
@jd jd deleted the fix-delay branch September 23, 2019 12:47
@majorgreys majorgreys added this to the 0.30.0 milestone Oct 7, 2019
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.

None yet

3 participants