Skip to content

Fix slurm partition metrics with proper name #20169

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

Merged
merged 9 commits into from
May 8, 2025
Merged

Conversation

steveny91
Copy link
Contributor

@steveny91 steveny91 commented Apr 28, 2025

What does this PR do?

Small fix to a tag that was named incorrectly. Also changes the name of a set of metrics. These metrics don't represent the cpu allocated etc, but more so the state of the node. Renamed the function since the purpose of it has now changed.

Revert this change. Should be handled in another PR
Copy link

codecov bot commented Apr 28, 2025

Codecov Report

Attention: Patch coverage is 92.30769% with 1 line in your changes missing coverage. Please review.

Project coverage is 85.41%. Comparing base (ea04835) to head (7b0d287).
Report is 3 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
activemq ?
aerospike ?
airflow ?
cassandra ?
cassandra_nodetool ?
ceph ?
cilium ?
clickhouse ?
confluent_platform ?
couchbase ?
dotnetclr ?
elastic ?
exchange_server ?
gearmand ?
gitlab ?
haproxy ?
hive ?
hivemq ?
hudi ?
ibm_ace ?
ibm_was ?
ignite ?
iis ?
jboss_wildfly ?
kafka ?
kafka_consumer ?
marklogic ?
mongo ?
mysql ?
openstack_controller ?
pdh_check ?
presto ?
rabbitmq ?
ray ?
sap_hana ?
scylla ?
slurm 90.41% <92.30%> (-0.09%) ⬇️
snmp ?
solr ?
sonarqube ?
sqlserver ?
teamcity ?
tomcat ?
vault ?
vertica ?
voltdb ?
vsphere ?
weblogic ?
windows_performance_counters ?
windows_service ?
zk ?

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@steveny91 steveny91 changed the title Sy/slurm node count fix Fix slurm partition metrics with proper name Apr 28, 2025
@steveny91 steveny91 marked this pull request as ready for review April 28, 2025 19:15
@steveny91 steveny91 requested a review from a team as a code owner April 28, 2025 19:15
Kyle-Neale
Kyle-Neale previously approved these changes Apr 29, 2025
@temporal-github-worker-1 temporal-github-worker-1 bot dismissed Kyle-Neale’s stale review April 29, 2025 19:20

Review from Kyle-Neale is dismissed. Related teams and files:

  • agent-integrations
    • slurm/changelog.d/20169.fixed
Kyle-Neale
Kyle-Neale previously approved these changes Apr 30, 2025
@temporal-github-worker-1 temporal-github-worker-1 bot dismissed Kyle-Neale’s stale review May 8, 2025 14:17

Review from Kyle-Neale is dismissed. Related teams and files:

  • agent-integrations
    • slurm/datadog_checks/slurm/check.py
    • slurm/datadog_checks/slurm/constants.py
    • slurm/metadata.csv
    • slurm/tests/common.py
@steveny91 steveny91 added this pull request to the merge queue May 8, 2025
Merged via the queue into master with commit e043fa7 May 8, 2025
37 checks passed
@steveny91 steveny91 deleted the sy/slurm-node-count-fix branch May 8, 2025 15:26
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