# How to ingest RSS and physical device data into ElasticSearch? **URL:** \ **Category:** Elasticsearch\ **Created:** [December 14, 2016, 3:10pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034 "2016-12-14T15:10:21Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![baden0x1](https://avatars.discourse-cdn.com/v4/letter/b/4da419/32.png) [@baden0x1](https://discuss.elastic.co/u/baden0x1)\ **Post date:** [December 14, 2016, 3:10pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034/1 "2016-12-14T15:10:21Z")
In v1.0 of a platform, we had a Windows service read from SQL Server settings to determine which RSS feeds request data from with filters and on a schedule. The feed locations and filters were all based on specific account-related settings. In working on the planning stages of a v2.0, I am going to be using the ELK stack as the foundation. As such, I am looking for suggestions on how to accomplish the same types of activities. For example, I have been reading about Beats and how it may be better than using LogStash for this. We will also be consuming data from physical devices as well, where they may report to the server, or the server may need to make a request to the devices. Can someone please lead me in the right direction for these requests? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 14, 2016, 10:04pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034/2 "2016-12-14T22:04:46Z")
> [@baden0x1](#): > > In v1.0 of a platform, we had a Windows service read from SQL Server settings to determine which RSS feeds request data from with filters and on a schedule. The feed locations and filters were all based on specific account-related settings. This sounds like something you would need to build. Logstash can make HTTP calls, but it cannot handle all the rest. > [@baden0x1](#): > > We will also be consuming data from physical devices as well, where they may report to the server, or the server may need to make a request to the devices. What data? ---
**Author:** ![baden0x1](https://avatars.discourse-cdn.com/v4/letter/b/4da419/32.png) [@baden0x1](https://discuss.elastic.co/u/baden0x1)\ **Post date:** [December 17, 2016, 1:39pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034/3 "2016-12-17T13:39:56Z")
In saying LogStash can handle HTTP calls - can these be based on database parameters that are sent to it or is Beats a better candidate? Data from physical sources may include things like a geo-location, some other identifiable fields and measurements. I suppose this could be shipped as a JSON object. Some devices can ship data, others we would need to request the data. I have been thinking of re-writing the Windows service using Task/Async architecture and using NEST to link up to ES, however, I would like to know some other ES-based options. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 17, 2016, 8:46pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034/4 "2016-12-17T20:46:42Z")
It might be easier to keep this in your other thread - [Can someone please explain the Beat architecture - Can a Beat be used to pull data from a list of sources?](https://discuss.elastic.co/t/can-someone-please-explain-the-beat-architecture-can-a-beat-be-used-to-pull-data-from-a-list-of-sources/69294/2) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 14, 2017, 8:47pm UTC](https://discuss.elastic.co/t/how-to-ingest-rss-and-physical-device-data-into-elasticsearch/69034/5 "2017-01-14T20:47:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.