Conversation
Neither +Inf nor NaN are valid custom values. Signed-off-by: beorn7 <beorn@grafana.com>
linasm
left a comment
There was a problem hiding this comment.
LGTM for the parts related to NHCB custom values (validation, reconciling).
I'm not familiar enough with counter reset hints, someone else should review that part.
|
Related question: it is not very clear from the spec, whether Also the spec should state that |
|
Right, we should make the handling of -Inf explicit (as we do for the standard exponential schemas). |
|
I added a commit for that. WRT -Inf as the 1st custom value: I think it should be allowed. That's implicit from the spec. I don't think we have to make it explicit in the spec. Just fix the Validate method. (Will create a PR momentarily.) |
|
I'll give prometheus/prometheus#17278 a final review ASAP. But since we already know that we want to merge it, this can be merged now, too. @krajorama maybe give it a final pass? |
d1fff25 to
90ac3c6
Compare
We originally planned to not include this in the initial feature set. But now prometheus/prometheus#17278 is underway, so let's aim for it. Signed-off-by: beorn7 <beorn@grafana.com>
Signed-off-by: beorn7 <beorn@grafana.com>
We are currently not really implementing this, but we should. It's just a minor issue, but see prometheus/prometheus#17308 to get it right. Signed-off-by: beorn7 <beorn@grafana.com>
90ac3c6 to
81031be
Compare
|
I manoeuvred GH into a state where it marks all my comments as "pending" but I cannot submit them. |
|
PHAL. |
krajorama
left a comment
There was a problem hiding this comment.
Small fix and an optional nit suggestion
beorn7
left a comment
There was a problem hiding this comment.
Thanks for the review.
However, I would like to keep both commented sections as they are. 😁
Signed-off-by: beorn7 <beorn@grafana.com>
81031be to
f24c4e6
Compare


See commit descriptions for details.
Let's only merge this once we are positive about how and when to tackle the related issues:
FYI: