Declare a runtime metric on its branch, and leave out a value that is… - #49
Merged
Merged
Conversation
… not known Every server spelled out the same shape by hand: an accessor whose block builds a CanopyMetric, sets its type and description and reads its value. Base, account, scheduler, AGSoilMetrics and now the metabase each had their own copy. CanopyBranchNode now says it once - gauge:description:reading:, counter:description:reading: and gauge:label:description:reading: for a map - and a server says only its name, what it means and where the number comes from. A metric whose value is nil answers no reading. A number that is not known yet is a gap in the series, not the word nil on the scrape and not a zero that claims to know. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
… not known
Every server spelled out the same shape by hand: an accessor whose block builds a CanopyMetric, sets its type and description and reads its value. Base, account, scheduler, AGSoilMetrics and now the metabase each had their own copy. CanopyBranchNode now says it once - gauge:description:reading:, counter:description:reading: and gauge:label:description:reading: for a map - and a server says only its name, what it means and where the number comes from.
A metric whose value is nil answers no reading. A number that is not known yet is a gap in the series, not the word nil on the scrape and not a zero that claims to know.