🎨Monitoring script: add json output for summary, allow to trigger computational cluster termination #7462
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sanderegg
added
t:maintenance
sanderegg
requested review from
YuryHrytsuk,
matusdrobuliak66,
mrnicegyu11 and
pcrespov
pcrespov
approved these changes
Apr 1, 2025
sanderegg
force-pushed
the
monitoring-script/add-json-output
branch
from
cc2a268 to
63f8883
Compare
|
This was referenced Apr 10, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 do these changes do?
The monitoring script has the following new features:
summarynow accepts--as-jsonargument and will output the current autoscaled clusters status as jsontrigger-cluster-terminationnow accepts aforceargument (to use with CARE) that will first cancel all the computation jobs for that user-id/wallet-id combination, then change the last heartbeat on the primary machine, thus trigger termination procedure from the clusters-keeper micro-serviceRelated issue/s
How to test
Dev-ops checklist