[SonarQube] Collect metrics of WORK_DUR #20368
Merged
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Add
WORK_DUR
to the list of the numeric types, to be able to collect additional metrics which are currently skipped.Motivation
WORK_DUR
stands for Working Duration and it represents the estimated effort required to fix issues or achieve certain quality objectives, which basically is an integer value.Some metrics like the following are skipped because their types are
WORK_DUR
which is not treated as a numeric type.new_technical_debt
: Added technical debteffort_to_reach_maintainability_rating_a
: Effort to Reach Maintainability Rating Asecurity_remediation_effort
: Security Remediation Effortintegrations-core/sonarqube/tests/api_responses/metrics_search_p_1
Lines 2 to 12 in 7207f56
Some of them are key metrics in SonarQube, and I'd like to have Datadog Agent to collect those too.
Test in my local environment
I've tested the change in my local environment and confirmed that it collects the values without any error.
Related PR
The numeric types were decided here and never had a new one after that.
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged