# Logstash http\_poller input / http filter design question

**URL:** <https://discuss.elastic.co/t/logstash-http-poller-input-http-filter-design-question/289012>\
**Category:** Logstash\
**Created:** [November 11, 2021, 6:16pm UTC](https://discuss.elastic.co/t/logstash-http-poller-input-http-filter-design-question/289012 "2021-11-11T18:16:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![byoungman](https://avatars.discourse-cdn.com/v4/letter/b/838e76/32.png) [@byoungman](https://discuss.elastic.co/u/byoungman)\
**Post date:** [November 11, 2021, 6:16pm UTC](https://discuss.elastic.co/t/logstash-http-poller-input-http-filter-design-question/289012/1 "2021-11-11T18:16:28Z")

</div>

Good Afternoon,

I am starting to pull in AppDynamics metric information into our Elastic stack for persistence purposes.

I have 5 metrics from each of 13 servers that I need to capture and my design in my Stage environment is that I have 2 config files - one for each metric I want to capture so what I am doing is making a call to the AppDynamics OAUTH API with the http\_poller to get a token that I then pass to the http filter to use to make the metric call.

This is fine for 2 metrics on one server but what I am looking at in my production environment would be 65 separate logstash.conf files one for each metric REST API call to AppDynamics. So my question is this - is there a more efficient way to accomplish this? Something similar to having one http\_poller file that would be able to send the token to the metric url's stored in another file as a hash (or something similar)?

Thanks,  
Bill

---

<div class="post-metadata">

**Author:** ![AquaX](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aquax/32/92006_2.png) [@AquaX](https://discuss.elastic.co/u/AquaX)\
**Post date:** [November 17, 2021, 1:16pm UTC](https://discuss.elastic.co/t/logstash-http-poller-input-http-filter-design-question/289012/2 "2021-11-17T13:16:52Z")

</div>

Absolutely! Logstash can do pipeline to pipeline communication where you can gather the tokens in one pipeline and then pass that information to the next pipeline for your API's.  
It's going to be a bit of work but it will probably work quite well.

Read this whole article:

> **[Pipeline-to-Pipeline Communication | Logstash Reference \[7.15\] | Elastic](https://www.elastic.co/guide/en/logstash/current/pipeline-to-pipeline.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:** [December 15, 2021, 1:17pm UTC](https://discuss.elastic.co/t/logstash-http-poller-input-http-filter-design-question/289012/3 "2021-12-15T13:17:02Z")

</div>

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