# Auditd module's kibana dashboards do not use keyword fields

**URL:** <https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795>\
**Category:** Beats\
**Tags:** auditbeat\
**Created:** [May 15, 2020, 10:47am UTC](https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795 "2020-05-15T10:47:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kosfar](https://avatars.discourse-cdn.com/v4/letter/k/edb3f5/32.png) [@kosfar](https://discuss.elastic.co/u/kosfar)\
**Post date:** [May 15, 2020, 10:47am UTC](https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795/1 "2020-05-15T10:47:23Z")

</div>

Kibana dashboards and visualizations for auditd module do not use keyword fields for aggregation queries in my version 6.8.4. This is the case for latest upstream too though:

> **[elastic/beats](https://github.com/elastic/beats/tree/master/auditbeat/module/auditd/_meta/kibana/7/dashboard)**
>
> :tropical\_fish: Beats - Lightweight shippers for Elasticsearch & Logstash - elastic/beats

This led to dashboards not working properly since fielddata is disabled by default for text fields. I managed to make them work again, by editing the jsons and using keyword fields.

Is there a reason that upstream uses text fields for aggregation queries ? Does it make sense to send a PR for it?

Thank you,  
Kostis

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [May 15, 2020, 3:40pm UTC](https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795/2 "2020-05-15T15:40:58Z")

</div>

What specific fields are seeing indexed as `text`? Most things are `keyword`, but there are a few places where multi-fields have been used to index both as `keyword` and `text`.

Maybe you don't have the Auditbeat [index template installed](https://www.elastic.co/guide/en/beats/auditbeat/7.7/auditbeat-template.html)?

---

<div class="post-metadata">

**Author:** ![kosfar](https://avatars.discourse-cdn.com/v4/letter/k/edb3f5/32.png) [@kosfar](https://discuss.elastic.co/u/kosfar)\
**Post date:** [May 16, 2020, 5:15pm UTC](https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795/3 "2020-05-16T17:15:18Z")

</div>

Ah yeah, that could be it, thanks! If Elasticsearch has already loaded documents,I guess I can load the template retroactively then, and Kibana will honor the new new template for new index documents? Is that right?

---

<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:** [June 6, 2020, 5:15pm UTC](https://discuss.elastic.co/t/auditd-modules-kibana-dashboards-do-not-use-keyword-fields/232795/4 "2020-06-06T17:15:19Z")

</div>

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