# Figure out which pipeline works the most?

**URL:** <https://discuss.elastic.co/t/figure-out-which-pipeline-works-the-most/276645>\
**Category:** Logstash\
**Created:** [June 22, 2021, 11:24am UTC](https://discuss.elastic.co/t/figure-out-which-pipeline-works-the-most/276645 "2021-06-22T11:24:41Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![McElroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mcelroy/32/24639_2.png) [@McElroy](https://discuss.elastic.co/u/McElroy)\
**Post date:** [June 22, 2021, 11:24am UTC](https://discuss.elastic.co/t/figure-out-which-pipeline-works-the-most/276645/1 "2021-06-22T11:24:41Z")

</div>

Hi,

we have a pretty old ELK-stack (5.5) and since a few weeks our Logstash CPU usage is through the roof. Is there a way to check which pipeline or grok pattern is causing that?

---

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [June 22, 2021, 12:42pm UTC](https://discuss.elastic.co/t/figure-out-which-pipeline-works-the-most/276645/2 "2021-06-22T12:42:21Z")

</div>

I think 5.5 had monitoring, but you're right, it's old. If monitoring was configured to send the stats to Elastic (or a monitoring stack) before problems occur, then you have "before" history. If not, this might help [Node Stats API | Logstash Reference [5.5] | Elastic](https://www.elastic.co/guide/en/logstash/5.5/node-stats-api.html)

---

<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 20, 2021, 12:42pm UTC](https://discuss.elastic.co/t/figure-out-which-pipeline-works-the-most/276645/3 "2021-07-20T12:42:23Z")

</div>

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