# Requirement to build logstah core module to generate a custom logstah for a specific purpose

**URL:** <https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200>\
**Category:** Logstash\
**Created:** [September 26, 2022, 6:37pm UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200 "2022-09-26T18:37:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rravitech](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rravitech/32/108994_2.png) [@rravitech](https://discuss.elastic.co/u/rravitech)\
**Post date:** [September 26, 2022, 6:37pm UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200/1 "2022-09-26T18:37:51Z")

</div>

I have a requirement to edit the logstash core, and generate a kind of build out of it.  
Need to customize logstash code to resist over the below mechanism.

Logstash has an at-least-once delivery model. Every event is sent to each output at least once.  
Where as what i need is.  
When one output is blocked, just ignore it and send the messages to other output system.

Can I customize the Logstash core code from the Logstash repo and generate build out of it. To achieve my requirement. ?

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [September 26, 2022, 7:07pm UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200/2 "2022-09-26T19:07:27Z")

</div>

> [@rravitech](#):
>
> Can I customize the Logstash core code from the Logstash repo and generate build out of it. To achieve my requirement. ?

I'm sure it is possible, but I would have no idea where to start.

You can also achieve it in logstash by linking a udp output to a udp input. See [this](https://discuss.elastic.co/t/logstash-multiple-pipelines-failure-with-persistent-queues/296520/2) thread.

---

<div class="post-metadata">

**Author:** ![rravitech](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rravitech/32/108994_2.png) [@rravitech](https://discuss.elastic.co/u/rravitech)\
**Post date:** [September 30, 2022, 7:31am UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200/3 "2022-09-30T07:31:30Z")

</div>

Thanks @Badger , let me try this approach and see.

---

<div class="post-metadata">

**Author:** ![Rios](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rios/32/95745_2.png) [@Rios](https://discuss.elastic.co/u/Rios)\
**Post date:** [September 30, 2022, 9:01am UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200/4 "2022-09-30T09:01:01Z")

</div>

If I get correctly LS logic, outputs are like independent plugins with own codes, logic and settings. For ES output, maybe to start [here](https://github.com/logstash-plugins/logstash-output-elasticsearch/blob/main/lib/logstash/outputs/elasticsearch/http_client/pool.rb).

---

<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:** [October 28, 2022, 9:01am UTC](https://discuss.elastic.co/t/requirement-to-build-logstah-core-module-to-generate-a-custom-logstah-for-a-specific-purpose/315200/5 "2022-10-28T09:01:38Z")

</div>

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