# Decorator for aggregated values

**URL:** https://discuss.elastic.co/t/decorator-for-aggregated-values/42712
**Category:** Kibana
**Created:** [February 25, 2016, 1:09pm UTC](https://discuss.elastic.co/t/decorator-for-aggregated-values/42712 "2016-02-25T13:09:58Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![feicipet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/feicipet/32/8056_2.png) [@feicipet](https://discuss.elastic.co/u/feicipet)
#### Post date: [February 25, 2016, 1:09pm UTC](https://discuss.elastic.co/t/decorator-for-aggregated-values/42712/1 "2016-02-25T13:09:58Z")

</div>

I have certain fields where the value is a numeric and it represents a certain status (e.g. 0 - OK, 1 - User Error, 2 - System Error etc). But if I show just the numeric value in a report, it's not really intuitive to interpret. I know that it's not possible to aggregate parent-children in Kibana right now, but is there a way that I can do a decorator so that I can manually map the values to show "OK" when the value is 0 ad so on? That would at least make it friendlier for a layman to view the dashboard.

Thanks  
Wong

---

<div class="post-metadata">

### Author: ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)
#### Post date: [February 26, 2016, 1:39am UTC](https://discuss.elastic.co/t/decorator-for-aggregated-values/42712/2 "2016-02-26T01:39:31Z")

</div>

I don't think you can currently do this, it's better to do it on the indexing side anyway.

What version are you on?

---

<div class="post-metadata">

### Author: ![feicipet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/feicipet/32/8056_2.png) [@feicipet](https://discuss.elastic.co/u/feicipet)
#### Post date: [February 26, 2016, 3:23am UTC](https://discuss.elastic.co/t/decorator-for-aggregated-values/42712/3 "2016-02-26T03:23:13Z")

</div>

I'm on Kibana version 4.4.1 / ES 2.2.

I assume doing it on the indexing side means directly creating a field for the expanded definitions of the original values? I've been doing that, but frankly speaking, it's creating a lot of work as the source data comes from a normalized database and there's a ton of such statuses which means my import scripts have been getting a lot more complicated just to denormalize the definition of statuses. Was wondering if there was a more efficient way to tackle this.

Thanks  
Wong

---

<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 6, 2017, 2:01pm UTC](https://discuss.elastic.co/t/decorator-for-aggregated-values/42712/4 "2017-07-06T14:01:03Z")

</div>


