# Logstash JDBC Input last\_run\_metadata\_path and Heroku

**URL:** <https://discuss.elastic.co/t/logstash-jdbc-input-last-run-metadata-path-and-heroku/174452>\
**Category:** Logstash\
**Created:** [March 29, 2019, 1:47am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-last-run-metadata-path-and-heroku/174452 "2019-03-29T01:47:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elseahawk](https://avatars.discourse-cdn.com/v4/letter/e/bc79bd/32.png) [@elseahawk](https://discuss.elastic.co/u/elseahawk)\
**Post date:** [March 29, 2019, 1:47am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-last-run-metadata-path-and-heroku/174452/1 "2019-03-29T01:47:27Z")

</div>

Hi,  
I am considering running our Logstash in a series of dedicated dynos on Heroku. But heroku's filesystem is ephemeral and is not persisted across dyno reboots. So I am wondering how people use logstash on heroku and what they do for the state tracking which typically is stored in last\_run\_metadata\_path?  
Thanks

---

<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:** [April 26, 2019, 1:47am UTC](https://discuss.elastic.co/t/logstash-jdbc-input-last-run-metadata-path-and-heroku/174452/2 "2019-04-26T01:47:35Z")

</div>

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