# Precision Threshold of Count in Canvas

**URL:** <https://discuss.elastic.co/t/precision-threshold-of-count-in-canvas/274664>\
**Category:** Kibana\
**Tags:** canvas\
**Created:** [June 1, 2021, 4:10pm UTC](https://discuss.elastic.co/t/precision-threshold-of-count-in-canvas/274664 "2021-06-01T16:10:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![poff](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/poff/32/81795_2.png) [@poff](https://discuss.elastic.co/u/poff)\
**Post date:** [June 2, 2021, 6:25pm UTC](https://discuss.elastic.co/t/precision-threshold-of-count-in-canvas/274664/4 "2021-06-02T18:25:19Z")

</div>

I just confirmed with the ES SQL team that aggregation like this is imprecise and unfortunately there isn't a way to tell the SQL endpoint to change the precision threshold. You might consider opening a ticket in the [elasticsearch github repo](https://github.com/elastic/elasticsearch) with this feature request for the SQL team.

As for the second example that uses the math function to count unique values, I'm a little surprised this isn't working. Are there any filters being passed in that would hide some expected data?

If all else fails and you were able to create a visualization outside of Canvas that pulls your data that you want, you can add that visualization directly to a workpad

---

_[View the full topic](https://discuss.elastic.co/t/precision-threshold-of-count-in-canvas/274664)._