# Elastic Agent - listen on tcp/9200?

**URL:** https://discuss.elastic.co/t/elastic-agent-listen-on-tcp-9200/345756
**Category:** Elastic Agent
**Created:** [October 25, 2023, 5:17pm UTC](https://discuss.elastic.co/t/elastic-agent-listen-on-tcp-9200/345756 "2023-10-25T17:17:54Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![dmgeurts](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dmgeurts/32/95115_2.png) [@dmgeurts](https://discuss.elastic.co/u/dmgeurts)
#### Post date: [October 25, 2023, 5:17pm UTC](https://discuss.elastic.co/t/elastic-agent-listen-on-tcp-9200/345756/1 "2023-10-25T17:17:54Z")

</div>

[Parsedmarc](https://github.com/domainaware/parsedmarc) can send to Elasticsearch using xpack, but rather than go through the pain of this I was hoping to use the Elastic Agent already installed on this server to do the shipping of the data.

Is there an Elastic Agent input that would provide a local means of shipping data normally sent directly to ELK on TCP:9200?

Or is this idea completely insane and absurd?

---

<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: [November 22, 2023, 5:18pm UTC](https://discuss.elastic.co/t/elastic-agent-listen-on-tcp-9200/345756/2 "2023-11-22T17:18:40Z")

</div>

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