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
NAMESPACE_QUERY("sum by (namespace) ( avg_over_time(kube_namespace_status_phase{namespace!=\"\" ADDITIONAL_LABEL}[15d]))"),
We are not generating recommendations using the above query; instead, we are requesting a list of all active namespaces. And 15d should not be considered
we gather container details based on the namespaces retrieved from the query. However, for a scenario where a user generates recommendations for a 15-day-old job via the UI, it makes sense to account for namespaces that might no longer be active.
In such cases, the query should ensure it fetches data from historical metrics as well, so that namespaces tied to past jobs are considered, even if they aren't currently active.
but as of bulk considers only active containers and namespaces recommendations only .
How to reproduce it
Create a namespace older than 15 days and call /bulk api and it fails
Expected behavior
Create a namespace older than 15 days and call /bulk api and it should gerneates recommendations
Describe the bug
sum by (namespace) ( avg_over_time(kube_namespace_status_phase{namespace!="" }[15d]
autotune/src/main/java/com/autotune/common/data/dataSourceQueries/DataSourceQueries.java
Line 10 in 268063a
We are not generating recommendations using the above query; instead, we are requesting a list of all active namespaces. And 15d should not be considered
we gather container details based on the namespaces retrieved from the query. However, for a scenario where a user generates recommendations for a 15-day-old job via the UI, it makes sense to account for namespaces that might no longer be active.
In such cases, the query should ensure it fetches data from historical metrics as well, so that namespaces tied to past jobs are considered, even if they aren't currently active.
but as of bulk considers only active containers and namespaces recommendations only .
How to reproduce it
Create a namespace older than 15 days and call /bulk api and it fails
Expected behavior
Create a namespace older than 15 days and call /bulk api and it should gerneates recommendations
Relevant logs
Environment:
Additional context
slack conversation log
The text was updated successfully, but these errors were encountered: