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
The utilization field being extracted is a float (ex: 55.4). The avg_over_time() appears to properly calculate the values for each individual stream, but when wrapped with a avg() to get the average across all of the streams the unimplemented error is returned instead.
Expected behavior
While wrapping an avg_over_time() with a avg() is probably not as good as avg_over_time() by (label), there is not an obvious reason why it should not work. I would expect an unwrapped float per log stream could be aggregated with avg().
Environment:
Infrastructure: EKS
Deployment tool: Raw manifests via ArgoCD
Work-around
Using avg_over_time(...) by (label) to aggregate instead of wrapping it with avg().
This might be related to #6130 and the changes in 2.4, but I haven't had a chance to test that yet.
The text was updated successfully, but these errors were encountered:
Describe the bug
After upgrading from 2.3 to 2.5, this query will result in an
unimplemented
error:The
utilization
field being extracted is a float (ex:55.4
). Theavg_over_time()
appears to properly calculate the values for each individual stream, but when wrapped with aavg()
to get the average across all of the streams theunimplemented
error is returned instead.To Reproduce
Steps to reproduce the behavior:
avg(avg_over_time{job="somejob" | json somefield="field" | unwrap somefield [$__interval]))
Expected behavior
While wrapping an
avg_over_time()
with aavg()
is probably not as good asavg_over_time() by (label)
, there is not an obvious reason why it should not work. I would expect an unwrapped float per log stream could be aggregated withavg()
.Environment:
Work-around
Using
avg_over_time(...) by (label)
to aggregate instead of wrapping it withavg()
.This might be related to #6130 and the changes in 2.4, but I haven't had a chance to test that yet.
The text was updated successfully, but these errors were encountered: