# Problem with unique count and cardinality

**URL:** <https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298>\
**Category:** Elasticsearch\
**Created:** [March 27, 2024, 2:43pm UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298 "2024-03-27T14:43:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_k/32/123676_2.png) [@Peter\_K](https://discuss.elastic.co/u/Peter_K)\
**Post date:** [March 27, 2024, 2:43pm UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298/1 "2024-03-27T14:43:03Z")

</div>

There are the following fields:

- documentnumber
- user (user identifier)
- @timestamp field

I want to create the following monitoring (as EQL or other query, as alert and if possible in dashboard form) in Kibana: Show the unique users and document numbers for which \>= 10 unique users request the same document number in the previous 24 hours.

When creating an aggregation in a visualization, a unique cardinality issue is encountered. This particularly occurs when the aggregation is performed on the Y-axis of a visualisation.

---

<div class="post-metadata">

**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\
**Post date:** [April 2, 2024, 5:36pm UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298/2 "2024-04-02T17:36:41Z")

</div>

Hi Peter K, you've tagged the question as "Enterprise App Search", but I see that your question is more of a general Elasticsearch question, is it correct?

---

<div class="post-metadata">

**Author:** ![Peter\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/peter_k/32/123676_2.png) [@Peter\_K](https://discuss.elastic.co/u/Peter_K)\
**Post date:** [April 3, 2024, 9:59am UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298/3 "2024-04-03T09:59:04Z")

</div>

That's correct, but could not choose Elasticsearch when creating the post

---

<div class="post-metadata">

**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\
**Post date:** [April 3, 2024, 10:14am UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298/4 "2024-04-03T10:14:55Z")

</div>

I've moved the topic into Stack / Elasticsearch, this would be the correct forum category for the question.

That will give more visibility to this post and increase likelihood of getting the answer you need!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 1, 2024, 10:15am UTC](https://discuss.elastic.co/t/problem-with-unique-count-and-cardinality/356298/5 "2024-05-01T10:15:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.