# Beats on Heroku (rails) **URL:** \ **Category:** Beats\ **Tags:** filebeat, heartbeat\ **Created:** [August 12, 2020, 8:12pm UTC](https://discuss.elastic.co/t/beats-on-heroku-rails/244780 "2020-08-12T20:12:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![weilandia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/weilandia/32/55574_2.png) [@weilandia](https://discuss.elastic.co/u/weilandia)\ **Post date:** [August 12, 2020, 8:12pm UTC](https://discuss.elastic.co/t/beats-on-heroku-rails/244780/1 "2020-08-12T20:12:22Z")
Is there a good way to setup Elastic beats (filebeat, heartbeat, etc.) on Heroku (rails app)? All the setup instructions have you download the packages and run the beat servers. Doing this for each Heroku dyno everytime a dyno restarts seems wrong to me, but unsure. Is there a better way? ---
**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\ **Post date:** [August 21, 2020, 1:22am UTC](https://discuss.elastic.co/t/beats-on-heroku-rails/244780/2 "2020-08-21T01:22:04Z")
I would look into using a [syslog drain](https://devcenter.heroku.com/articles/log-drains#syslog-drains) and sending that to filebeat running on another server. Heroku doesn't seem like a good fit for Heatbeat IMHO, it'd make more sense to put that on a standard virtual instance. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [September 18, 2020, 3:22am UTC](https://discuss.elastic.co/t/beats-on-heroku-rails/244780/3 "2020-09-18T03:22:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.