Open jalev opened 7 months ago
Hi @jalev this is weird as in my case scope=~"resource|"
matches exactly both when the scope
label equals resource
and when it is empty. I'm experiencing a greater than 100% availability sporadically too, though I've tracked it down to a difference between cluster_verb_scope_le:apiserver_request_sli_duration_seconds_bucket:increase30d{le="+Inf"}
and cluster_verb_scope:apiserver_request_sli_duration_seconds_count:increase30d
, while they should be equal (still I am not sure of the issue, but it might be related to this one here. Did you check this is not your case too?
I'll take a look and come back 👍
This PR has been automatically marked as stale because it has not had any activity in the past 30 days. The next time this stale check runs, the stale label will be removed if there is new activity. The issue will be closed in 7 days if there is no new activity. Thank you for your contributions!
The current behaviour of
scope=~"resource|"
does not match anything even if there is aresource
label, and so will always returnvector(0)
. This makes the calculations go into negative numbers which makes the availability numbers return a value>1
:When you change the matcher to
scope="resource"
:This is also true for other things with the
scope=~"resource|"
. E.g. the error burndown:and after fixing the query: