-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add support for target_info metric w/ shared label cache #19397
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
…g/integrations-core into UTXOnly/openmetrics-target-info-4
is it possible to have more than 1 target_info entry? Or would there always be 1 only per payload? |
datadog_checks_base/tests/base/checks/openmetrics/test_v2/test_options.py
Outdated
Show resolved
Hide resolved
…_options.py Co-authored-by: Steven Yuen <steven.yuen@datadoghq.com>
Review from steveny91 is dismissed.
Related teams and files:
- agent-integrations
- datadog_checks_base/tests/base/checks/openmetrics/test_v2/test_options.py
* Collect target info metric * Corrected cache error * Log cleanup * Debug log cleanup * Add tests to test cache w/ target_info * Add test for unordered target info with cache shared labels * Add transformer for info metric type * Cleaned but not working first iteration * Refactor tag caching logic * Validate type for config options * Added changelog entry * Fix validate shared labels failing test * Fix whitespace causing lint failure * Fix target info with cache, add tests * Linting * Cleanup debug log * Comment cleanup * Refactor label population * Reformat imports * Reorder target_info_labels definition * Add consume w/ target info method * Add comments * Update datadog_checks_base/tests/base/checks/openmetrics/test_v2/test_options.py Co-authored-by: Steven Yuen <steven.yuen@datadoghq.com> * lint test --------- Co-authored-by: Steven Yuen <steven.yuen@datadoghq.com> d802c07
What does this PR do?
target_info
typeMotivation
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