You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
If a query is sharded and returns annotations, the annotations do not include position information.
For example, running the query sum(rate(foo[1m])) without sharding returns the annotation metric might not be a counter, name does not end in _total/_sum/_count/_bucket: "foo" (1:10), where the (1:10) refers to the position in the expression that the annotation relates to.
However, if the same query is run without sharding, then the annotation does not include position information. This can make it harder to understand what the annotation is referring to.
Describe the solution you'd like
Include position information in annotations returned for sharded queries.
Is your feature request related to a problem? Please describe.
If a query is sharded and returns annotations, the annotations do not include position information.
For example, running the query
sum(rate(foo[1m]))
without sharding returns the annotationmetric might not be a counter, name does not end in _total/_sum/_count/_bucket: "foo" (1:10)
, where the(1:10)
refers to the position in the expression that the annotation relates to.However, if the same query is run without sharding, then the annotation does not include position information. This can make it harder to understand what the annotation is referring to.
Describe the solution you'd like
Include position information in annotations returned for sharded queries.
Describe alternatives you've considered
(none)
Additional context
Discussed further here: #9138 (comment)
The text was updated successfully, but these errors were encountered: