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

Convert jmx to in-app types for replay_check_run #7275

Merged
merged 5 commits into from
Aug 5, 2020

Conversation

AlexandreYang
Copy link
Member

@AlexandreYang AlexandreYang commented Aug 4, 2020

What does this PR do?

Convert jmx to in-app types

See test results here: #7277

Motivation

replay_check_run should return in-app types

Additional info

There was an attempt to harmonise the metrics on jmxfetch side, but the PR has been finalised closed to avoid adding complexity in jmxfetch: DataDog/jmxfetch#281

@codecov
Copy link

codecov bot commented Aug 4, 2020

Codecov Report

Merging #7275 into master will decrease coverage by 7.08%.
The diff coverage is 30.76%.

Impacted Files Coverage Δ
activemq/tests/test_check.py 50.00% <0.00%> (ø)
solr/tests/test_check.py 53.84% <0.00%> (ø)
datadog_checks_dev/datadog_checks/dev/_env.py 62.33% <20.00%> (-2.05%) ⬇️
ignite/tests/test_check.py 40.00% <40.00%> (+6.66%) ⬆️
ignite/tests/common.py 100.00% <100.00%> (ø)
...master/datadog_checks/mesos_master/mesos_master.py
etcd/datadog_checks/etcd/metrics.py
linux_proc_extras/tests/conftest.py
cacti/tests/test_cacti.py
directory/tests/common.py
... and 706 more

ignite.threads.tasks,count,10,task,,Approximate total number of tasks that have been scheduled for execution.,0,ignite,
ignite.threads.completed_tasks,count,10,task,,Approximate total number of tasks that have completed execution.,0,ignite,
ignite.threads.tasks,rate,10,task,,Approximate total number of tasks that have been scheduled for execution.,0,ignite,
ignite.threads.completed_tasks,rate,10,task,,Approximate total number of tasks that have completed execution.,0,ignite,
Copy link
Member Author

Choose a reason for hiding this comment

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

Fixing metadata.csv: JMX monotonic_count -> DSD count -> in-app rate

Copy link
Contributor

Choose a reason for hiding this comment

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

but wasnt this causing an override?

Copy link
Member Author

@AlexandreYang AlexandreYang Aug 4, 2020

Choose a reason for hiding this comment

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

@hithwen

Before this change, we were trying to compare monotonic_count (from Agent check) to count (from metadata.csv)

Now with this change, we are trying to compare monotonic_count (from Agent check) converted to rate to rate (from metadata.csv)

@AlexandreYang AlexandreYang force-pushed the alex/jmx_assert_metrics_using_metadata branch from 9714b9a to 4fa3337 Compare August 4, 2020 13:48
@AlexandreYang AlexandreYang merged commit 38076dc into master Aug 5, 2020
@AlexandreYang AlexandreYang deleted the alex/jmx_assert_metrics_using_metadata branch August 5, 2020 09:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants