-
Notifications
You must be signed in to change notification settings - Fork 13
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
In Details, report threshold #39
Comments
Our team had a discussion about reporting threshold values this morning and reached the consensus that it was important to have both the So we'd like to see the a |
Interesting idea, but I think it should be failRange and passRange otherwise directionality etc. may become a problem and range seems to provide more flexibility, anyway |
@inadarei Is there a need to account for hysteresis? In any case, our team has implemented this under the auspices of section 4.10 of the specification. Clearly the specification can't provide named fields for everything someone might need but this request might be common enough to warrant adding to the spec. |
Can you share details on how you implemented failThreshold and passThreshold? How does a client know if "more than" that value is good, or "less than" that value is good? Thank you |
They're more intended for humans to read ... the request was "we want to know how close to a |
The Details structure could report an optional theshold to understand at what level the status changed from
pass
towarn
.This would change 4.4. second sentence to "Clarifies the unit of measureent in which observedValue and threshold are reported, [...]".
This would add a section to chapter 4. Details:
"4.X thresholdValue
thresholdValue: (optional) could be any valid JSON value, such as: string, number, object, array or literal. This value is used to tell the value above or below which the observedValue would change the status from pass to warn."
I had the idea when looking at the cpu utilization in the example and thought of implementing it.
The text was updated successfully, but these errors were encountered: