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

[CONTP-60] New unscheduled config telemetry #19306

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

gabedos
Copy link
Contributor

@gabedos gabedos commented Dec 24, 2024

What does this PR do?

Adds telemetry for cluster check configs that have been dangling after an extended number of rescheduling attempts.
This metric will follow the form cluster_checks_configs_extended_dangling{config_name, config_source, join_leader}

Motivation

Provide higher level of visibility into cluster check dispatching

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

Copy link

codecov bot commented Dec 24, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.63%. Comparing base (1cb058e) to head (25e13c5).

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
datadog_cluster_agent 90.19% <ø> (ø)
hive ?
hivemq ?
hudi ?
ignite ?
jboss_wildfly ?
kafka ?
presto ?
solr ?

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

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.

1 participant