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

Open
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 longer than expected and are then classified as an unscheduled check.
This metric will follow the form cluster_checks_unscheduled_check{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 (8fa96b2).
Report is 10 commits behind head on master.

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.

@gabedos gabedos force-pushed the gabedos/add-cluster-check-telemetry branch from 25e13c5 to 895fb53 Compare December 30, 2024 14:48
@gabedos gabedos marked this pull request as ready for review December 30, 2024 14:50
@gabedos gabedos requested review from a team as code owners December 30, 2024 14:50
datadog.cluster_agent.workloadmeta.notifications_sent,count,,,,Number of notifications sent by workloadmeta to its subscribers,0,datadog_cluster_agent,workloadmeta notifications sent,
datadog.cluster_agent.workloadmeta.stored_entities,gauge,,,,Number of entities stored in workloadmeta,0,datadog_cluster_agent,workloadmeta stored entities,
datadog.cluster_agent.workloadmeta.subscribers,gauge,,,,Number of workloadmeta subscribers,0,datadog_cluster_agent,workloadmeta subscribers,
metric_name,metric_type,interval,unit_name,per_unit_name,description,orientation,integration,short_name,curated_metric,sample_tags
Copy link
Member

Choose a reason for hiding this comment

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

question: which metrics are using sample_tags currently?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My last commit complained for me to run ddev validate metadata datadog_cluster_agent --sync and it produced this sample tags field (I have no idea why). I can go an manually remove it.

Copy link
Member

@jennchenn jennchenn Dec 30, 2024

Choose a reason for hiding this comment

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

Ah just found this PR #17521; seems like--sync will automatically add the column, but for existing files it's fine with or without. Not sure if sample_tags should be added to all metadata.csv files going forward so can wait for agent-integrations to chime in before you make changes manually (I was mostly just curious how this column got added)!

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.

2 participants