# How to use terms as filter item?

**URL:** <https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417>\
**Category:** Kibana\
**Tags:** rollups\
**Created:** [June 7, 2023, 9:23am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417 "2023-06-07T09:23:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![kain\_su](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kain_su/32/121944_2.png) [@kain\_su](https://discuss.elastic.co/u/kain_su)\
**Post date:** [June 7, 2023, 9:23am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/1 "2023-06-07T09:23:54Z")

</div>

When I just filter terms\_A : \*, lens returns this error response, but I can show count of terms\_A records, does anyone knows what happened?

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/1/5/15e8d5b9699aa9a63d13586b4d5b74ffcc3970e1.png)

---

<div class="post-metadata">

**Author:** ![ppisljar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppisljar/32/11588_2.png) [@ppisljar](https://discuss.elastic.co/u/ppisljar)\
**Post date:** [June 7, 2023, 9:54am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/2 "2023-06-07T09:54:48Z")

</div>

Can you please provide more details about your dataset, chart configuration and the steps to take to recreate the issue.

---

<div class="post-metadata">

**Author:** ![kain\_su](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kain_su/32/121944_2.png) [@kain\_su](https://discuss.elastic.co/u/kain_su)\
**Post date:** [June 7, 2023, 10:30am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/3 "2023-06-07T10:30:18Z")

</div>

![image](https://us1.discourse-cdn.com/elastic/original/3X/a/8/a8593fd82a14ebd9789b9940b495a35746fa1829.png)  
and my rollup job json is like below

```auto
{
  "config": {
    "id": "rollup_apm_transactions_every_10m",
    "index_pattern": "traces-apm-*",
    "rollup_index": "rollup_apm_transactions_every_10m",
    "cron": "0 0/10 * * * ?",
    "groups": {
      "date_histogram": {
        "fixed_interval": "10m",
        "field": "@timestamp",
        "delay": "20s",
        "time_zone": "UTC"
      },
      "terms": {
        "fields": [
          "service.name"
        ]
      }
    },
    "metrics": [
     Omitted...
    ],
    "timeout": "20s",
    "page_size": 10000
  }
}

```

---

<div class="post-metadata">

**Author:** ![ppisljar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppisljar/32/11588_2.png) [@ppisljar](https://discuss.elastic.co/u/ppisljar)\
**Post date:** [June 8, 2023, 9:28am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/4 "2023-06-08T09:28:42Z")

</div>

can you please open a bug report here [GitHub - elastic/kibana: Your window into the Elastic Stack](https://github.com/elastic/kibana)  
it seems rollup indexes don't support the query we use for autosuggesting values for filters on some fields.

---

<div class="post-metadata">

**Author:** ![kain\_su](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kain_su/32/121944_2.png) [@kain\_su](https://discuss.elastic.co/u/kain_su)\
**Post date:** [June 16, 2023, 5:41am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/5 "2023-06-16T05:41:31Z")

</div>

Sorry to reply so late, and I faced another question is I can't aggregate the rollup data with an interval that is greater-than or equal to the configured rollup interval.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/8/e816a9602051957692aa20642c9d7be3614e6df4.png)

---

<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:** [July 14, 2023, 5:42am UTC](https://discuss.elastic.co/t/how-to-use-terms-as-filter-item/335417/6 "2023-07-14T05:42:24Z")

</div>

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