# How to tell, whether my Logstash instance ready? **URL:** \ **Category:** Logstash\ **Created:** [July 29, 2015, 3:16pm UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501 "2015-07-29T15:16:10Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pradeepfn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pradeepfn/32/3900_2.png) [@pradeepfn](https://discuss.elastic.co/u/pradeepfn)\ **Post date:** [July 29, 2015, 3:16pm UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501/1 "2015-07-29T15:16:11Z")
I want to determine whether my Logstash instance is ready for input data processing. In a manual installation, i look at the start-up logs and figure it out. Now i want to do the same programatically, for an orchestration scenario. How to programatically determine whether my newly spawned logstash instance is ready for input message processing. (Based on the input filter config, the Logstash start-up time varies significantly ) Thanks in advance.. ---
**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\ **Post date:** [July 29, 2015, 3:18pm UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501/2 "2015-07-29T15:18:35Z")
There's no API or similar for this, but you could set up a simple udp och tcp input that you could send a message to and route those messages to something that's convenient for you to monitor. Try to send a message once a second or so and when the message gets through you know everything is up. ---
**Author:** ![Joe\_Lawson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_lawson/32/3390_2.png) [@Joe\_Lawson](https://discuss.elastic.co/u/Joe_Lawson)\ **Post date:** [July 29, 2015, 7:07pm UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501/3 "2015-07-29T19:07:20Z")
You could try using the heartbeat plugin. For instance if you are using AWS Cloudformation have the heartbeat plugin hit the success url and then you would know it started. > **[How to check Logstash's pulse | Elastic](https://www.elastic.co/blog/how-to-check-logstashs-pulse)** > > The heartbeat plugin is a new way to monitor Logstash availability and throughput. ---
**Author:** ![Joe\_Lawson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_lawson/32/3390_2.png) [@Joe\_Lawson](https://discuss.elastic.co/u/Joe_Lawson)\ **Post date:** [July 29, 2015, 7:10pm UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501/4 "2015-07-29T19:10:18Z")
More info, for autoscaling use a creation policy: [http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-attribute-creationpolicy.html) a wait condition: [http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-waitcondition.html](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-waitcondition.html) and a wait condition handle: [http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-waitconditionhandle.html](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-waitconditionhandle.html) The handle will have a url as shown here [http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-waitcondition.html](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-waitcondition.html) and just use this output: [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-http.html) ---
**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:33am UTC](https://discuss.elastic.co/t/how-to-tell-whether-my-logstash-instance-ready/26501/5 "2017-07-06T05:33:27Z")