# Suggestions for visualizing complex query - Kubernetes cpu requested vs available

**URL:** https://discuss.elastic.co/t/suggestions-for-visualizing-complex-query-kubernetes-cpu-requested-vs-available/223416
**Category:** Kibana
**Created:** [March 12, 2020, 8:58pm UTC](https://discuss.elastic.co/t/suggestions-for-visualizing-complex-query-kubernetes-cpu-requested-vs-available/223416 "2020-03-12T20:58:47Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![Marius\_Dragomir](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marius_dragomir/32/42087_2.png) [@Marius\_Dragomir](https://discuss.elastic.co/u/Marius_Dragomir)
#### Post date: [March 13, 2020, 12:52am UTC](https://discuss.elastic.co/t/suggestions-for-visualizing-complex-query-kubernetes-cpu-requested-vs-available/223416/2 "2020-03-13T00:52:05Z")

</div>

A TSVB visualization with Math aggregation should pretty cover the case.  
Something like in this post:

> [@Percentages per day (per bucket) possible?](https://discuss.elastic.co/t/percentages-per-day-per-bucket-possible/208138/2):
>
> You can try with TSVB and the Math aggregation. Then you should be able to calculate the percentage of spam as "100 \* sum(spam)/sum(total\_volume)". Basically create 2 sum metrics, one for spam, one for total\_volume. Then create a math aggregation with the equivalent of the formula that I added above, and then keep just this line visible on the chart. PS: don't forget to keep the bucket size to 1d.

---

_[View the full topic](https://discuss.elastic.co/t/suggestions-for-visualizing-complex-query-kubernetes-cpu-requested-vs-available/223416)._