# Best Practice Configuration of Twitter Plugin for multiple twitter sources **URL:** \ **Category:** Logstash\ **Created:** [December 8, 2015, 12:21pm UTC](https://discuss.elastic.co/t/best-practice-configuration-of-twitter-plugin-for-multiple-twitter-sources/36631 "2015-12-08T12:21:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![mob](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@mob](https://discuss.elastic.co/u/mob)\ **Post date:** [December 8, 2015, 12:21pm UTC](https://discuss.elastic.co/t/best-practice-configuration-of-twitter-plugin-for-multiple-twitter-sources/36631/1 "2015-12-08T12:21:39Z")
Hi all, I've been looking for a reason to try ELK for a while now and finally have a small project I think would suit. I need to collect twitter data over a 2 week period but I'm not sure whats the best way to configure Logstash so it will work but won't exceed the twitter api resource limits. I need to monitor a few accounts (3 or 4) as well as collect tweets that mention specific tags (3 or 4). I don't expect the dataset to be massive or the rate of production to be intensive but I'm not sure do I use 1 logstash to collect everything or separate ones for each account and tag I need. Also does the twitter plugin play well with the twitter api resource constraints ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 5:19am UTC](https://discuss.elastic.co/t/best-practice-configuration-of-twitter-plugin-for-multiple-twitter-sources/36631/2 "2017-07-06T05:19:33Z")