# Field name changes upon rollup

**URL:** <https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570>\
**Category:** Kibana\
**Created:** [July 2, 2019, 6:54pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570 "2019-07-02T18:54:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcguacon](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@mcguacon](https://discuss.elastic.co/u/mcguacon)\
**Post date:** [July 2, 2019, 6:54pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/1 "2019-07-02T18:54:36Z")

</div>

I specify a field to be included in a rollup job. Example: windows.service.display\_name  
Then, when looking through the rolled up index, that data is under the field: windows.service.display\_name.terms.value

I haven't been able to find a good answer to this. Thanks.

---

<div class="post-metadata">

**Author:** ![jen-huang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jen-huang/32/74327_2.png) [@jen-huang](https://discuss.elastic.co/u/jen-huang)\
**Post date:** [July 2, 2019, 7:05pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/2 "2019-07-02T19:05:09Z")

</div>

This is expected behavior. Rollup indices have special internal field naming which are different from original field names. However you can still query (and visualize) against the original field names.

---

<div class="post-metadata">

**Author:** ![mcguacon](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@mcguacon](https://discuss.elastic.co/u/mcguacon)\
**Post date:** [July 2, 2019, 7:12pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/3 "2019-07-02T19:12:27Z")

</div>

Okay, then is it still possible to create a visualization with both 'live' and rolled up data if the field names differ?

---

<div class="post-metadata">

**Author:** ![jen-huang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jen-huang/32/74327_2.png) [@jen-huang](https://discuss.elastic.co/u/jen-huang)\
**Post date:** [July 2, 2019, 7:14pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/4 "2019-07-02T19:14:40Z")

</div>

Yes it is! You simply need to create an index pattern with the rollup index name, plus the live data wildcard, for example `rollup_logstash,logstash-*`. The index pattern will populate the normal field names. Example in docs: [https://www.elastic.co/guide/en/kibana/current/visualize-rollup-data.html](https://www.elastic.co/guide/en/kibana/current/visualize-rollup-data.html)

---

<div class="post-metadata">

**Author:** ![mcguacon](https://avatars.discourse-cdn.com/v4/letter/m/958977/32.png) [@mcguacon](https://discuss.elastic.co/u/mcguacon)\
**Post date:** [July 2, 2019, 7:16pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/5 "2019-07-02T19:16:08Z")

</div>

Okay, so it 'auto-magically' knows which names to map then for visualizations?  
Thanks for that info!

---

<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 30, 2019, 7:20pm UTC](https://discuss.elastic.co/t/field-name-changes-upon-rollup/188570/6 "2019-07-30T19:20:05Z")

</div>

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