# Using DataDog's vector to ship logs to ElasticSearch instead of elastic-agent?

**URL:** <https://discuss.elastic.co/t/using-datadogs-vector-to-ship-logs-to-elasticsearch-instead-of-elastic-agent/341388>\
**Category:** Logs\
**Created:** [August 22, 2023, 2:56pm UTC](https://discuss.elastic.co/t/using-datadogs-vector-to-ship-logs-to-elasticsearch-instead-of-elastic-agent/341388 "2023-08-22T14:56:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Craig\_Rodrigues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/craig_rodrigues/32/121875_2.png) [@Craig\_Rodrigues](https://discuss.elastic.co/u/Craig_Rodrigues)\
**Post date:** [August 22, 2023, 4:17pm UTC](https://discuss.elastic.co/t/using-datadogs-vector-to-ship-logs-to-elasticsearch-instead-of-elastic-agent/341388/3 "2023-08-22T16:17:46Z")

</div>

Thanks @leandrojmp , as usual your response is very accurate and useful.

In some cases, I have systems that are producing massive quantities of logs.  
In those cases I have seen Elastic-Agent 8.4.2 become a zombie process  
and sometimes elastic-agent uses so much CPU that it starves other components on the system.

I have upgraded my system to to Elastic 8.9.0 and my agents to Elastic-Agent 8.9.0, so hopefully  
the problems I saw with 8.4.2 are gone.

But at the same time I am looking at alternatives to elastic-agent for shipping logs to Elasticsearch.

I may be able to live without some of the features like custom pipelines and integrations for this particular use case.

---

_[View the full topic](https://discuss.elastic.co/t/using-datadogs-vector-to-ship-logs-to-elasticsearch-instead-of-elastic-agent/341388)._
