# \[suggestion\] custom pipeline labels/aliases/names in STATS API

**URL:** <https://discuss.elastic.co/t/suggestion-custom-pipeline-labels-aliases-names-in-stats-api/63991>\
**Category:** Logstash\
**Created:** [October 26, 2016, 10:48am UTC](https://discuss.elastic.co/t/suggestion-custom-pipeline-labels-aliases-names-in-stats-api/63991 "2016-10-26T10:48:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shog/32/12138_2.png) [@shog](https://discuss.elastic.co/u/shog)\
**Post date:** [October 26, 2016, 10:48am UTC](https://discuss.elastic.co/t/suggestion-custom-pipeline-labels-aliases-names-in-stats-api/63991/1 "2016-10-26T10:48:54Z")

</div>

Hi,

First of all thanks for providing new stats API, especially all the stats related to pipeline processing.  
This is super awesome! I already made a lot of improvements by investigating biggest time consumers.

I have one suggestion however; could you consider possibility to add custom names/aliases for those rule stats?

Why this may be good you ask? I'm working on LS Diamond collector similar to ES one from [https://github.com/python-diamond/Diamond/tree/master/src/collectors/elasticsearch](https://github.com/python-diamond/Diamond/tree/master/src/collectors/elasticsearch) that will graph all of those stats, but that won't be very useful for pipeline stats shifting names with any config addition.

So having a (possibility to add a) consistent name here would help a lot to keep/analyze some long-term metrics.

---

<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, 4:32am UTC](https://discuss.elastic.co/t/suggestion-custom-pipeline-labels-aliases-names-in-stats-api/63991/2 "2017-07-06T04:32:39Z")

</div>

Closed on July 6, 2017, 4:32am UTC