[Kubernetes][Dashboard] Fix proxy, controller manager and scheduler dashboards to support TSDB - #5992
Conversation
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
🌐 Coverage report
|
drewdaemon
left a comment
There was a problem hiding this comment.
No problems from my end!
|
I would suggest to change the labels of "Average Request" to "Max Average Request" . In general you can add the |
…11ed-b760-5d1bccb47f56.json Co-authored-by: Andrew Gizas <andreas.gkizas@elastic.co>
I think that might be confusing. Since it is a counter this |
|
@constanca-m I would say the opposite. The last value can be diffrent than the max and can lead to totally diffrent results in the calculation. For eg. last value of cpu can be something low but the max could have been a spike for the given period. So users should understand what they see |
|
I am not sure I understand. Since |
|
Ah indeed is a counter, was not paying attention. What happens if the counter resets to zero for example? |
|
That will be a problem @gizas, but I don't see a workaround for that right now. |
Signed-off-by: constanca-m <constanca.manteigas@elastic.co>
…fix-kubernetes-dashboards
| } | ||
| }, | ||
| "formula": "last_value(kubernetes.proxy.sync.networkprogramming.duration.us.sum)/(pick_max(last_value(kubernetes.proxy.sync.networkprogramming.duration.us.count),1))/1000000", | ||
| "formula": "max(kubernetes.proxy.sync.networkprogramming.duration.us.sum)/(pick_max(max(kubernetes.proxy.sync.networkprogramming.duration.us.count),1))/1000000", |
There was a problem hiding this comment.
if last_value is already supported, according to elastic/kibana#156168, why it was changed here last_value -> max?
There was a problem hiding this comment.
it is not critical because of this explanation #5992 (comment), trying to understand if there is any other reason
There was a problem hiding this comment.
When I pushed the changes, last value was still not available @tetianakravchenko, but that should be the correct aggregation. I will check that now.
Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
|
Package kubernetes - 1.37.0 containing this change is available at https://epr.elastic.co/search?package=kubernetes |
…ashboards to support TSDB (elastic#5992) * Fix proxy dashboard Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * Fix controller manager dashboard Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * Fix scheduler dashboard Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * Fix version Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * Update changelog Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * Update packages/kubernetes/kibana/dashboard/kubernetes-bf9389f0-0c14-11ed-b760-5d1bccb47f56.json Co-authored-by: Andrew Gizas <andreas.gkizas@elastic.co> * Switch max to last value. Signed-off-by: constanca-m <constanca.manteigas@elastic.co> * fix package version in manifest Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co> --------- Signed-off-by: constanca-m <constanca.manteigas@elastic.co> Signed-off-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co> Co-authored-by: Andrew Gizas <andreas.gkizas@elastic.co> Co-authored-by: Tetiana Kravchenko <tetiana.kravchenko@elastic.co>
What does this PR do?
In proxy, controller manager and scheduler dashboards, there are some visualizations that use
counterfields with now unsupported formulas -sumandlast_value- when TSDB is enabled. This PR fixes those issues so we can have similar visualizations for the same metrics.Checklist
changelog.ymlfile.How to test this PR locally
elastic-package buildinside Kubernetes package.elastic-package stack up -v -d --version=8.8.0-SNAPSHOT.Related issues
Screenshots
These screenshots only include the before/after of the broken visualizations. Others that used a
counterwithlast_valuewere switched tomax, but there was no change in the visualization. This is needed becauselast_valueis also no longer supported forcounterfields once TSDB is enabled.Proxy dashboard
Before:

After:

Note: "No results found" is shown because there are no documents for the applied filter in these two visualizations. There is nothing wrong with them.
Controller manager dashboard
Before:


After:


Note: Since we can no longer use
sumwe have to breakdown the metrics by the labels. This will likely lead to very confusing visualizations but as of now, there is no workaround.Scheduler dashboard
Before:



After:


