# Logstash Health Report API - Not Found **URL:** \ **Category:** Logstash\ **Created:** [January 8, 2025, 5:29pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952 "2025-01-08T17:29:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [January 8, 2025, 5:29pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/1 "2025-01-08T17:29:29Z")
ELK version : 8.15 Below API is giving the Not Found Output . curl -XGET 'localhost:9600/\_health\_report?pretty' While below api is working and giving output curl -XGET 'localhost:9600/?pretty' ---
**Author:** ![Trevor\_Blackford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trevor_blackford/32/120087_2.png) [@Trevor\_Blackford](https://discuss.elastic.co/u/Trevor_Blackford)\ **Post date:** [January 8, 2025, 5:41pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/2 "2025-01-08T17:41:58Z")
The health report is available as of 8.16 > **[Logstash 8.16.0 Release Notes | Logstash Reference \[8.16\] | Elastic](https://www.elastic.co/guide/en/logstash/8.16/logstash-8-16-0.html#health-api-8-16-0)** ---
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [January 8, 2025, 6:14pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/3 "2025-01-08T18:14:25Z")
Oh my mistake didn’t see ---
**Author:** ![Trevor\_Blackford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trevor_blackford/32/120087_2.png) [@Trevor\_Blackford](https://discuss.elastic.co/u/Trevor_Blackford)\ **Post date:** [January 8, 2025, 6:37pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/4 "2025-01-08T18:37:17Z")
Please let us know what you think! We're very excited to have this out for users and think it will make managing a Logstash deployment a lot easier. ---
**Author:** ![Aniket\_Pant](https://avatars.discourse-cdn.com/v4/letter/a/77aa72/32.png) [@Aniket\_Pant](https://discuss.elastic.co/u/Aniket_Pant)\ **Post date:** [January 9, 2025, 5:20am UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/5 "2025-01-09T05:20:23Z")
Hi @Trevor_Blackford , We are dealing with lag , when Logstash pick the data from kafka and send it to Elasticsearch and after that it visible in kibana . There is no issue in Elasticsearch we are using hot warm nodes in our cluster and we don’t know in Logstash where is the issue. When we going to upgrade ELK to 8.16 i hope using this API will tell something about the pipeline and we can take necessary action. ---
**Author:** ![Trevor\_Blackford](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trevor_blackford/32/120087_2.png) [@Trevor\_Blackford](https://discuss.elastic.co/u/Trevor_Blackford)\ **Post date:** [January 10, 2025, 4:40pm UTC](https://discuss.elastic.co/t/logstash-health-report-api-not-found/372952/6 "2025-01-10T16:40:24Z")
The overall health stats will notify you of a problem, but since you are experiencing throughput issues, you'll likely be directed to the this API for troubleshooting help [Node Stats API | Logstash Reference [8.17] | Elastic](https://www.elastic.co/guide/en/logstash/current/node-stats-api.html) Flow metrics in particular are helpful here - you can see the duration of event processing and queue backpressure. These data are available in an easy to use dashboard through the Logstash integration in Kibana [https://www.elastic.co/guide/en/logstash/current/dashboard-monitoring-with-elastic-agent.htm](https://www.elastic.co/guide/en/logstash/current/dashboard-monitoring-with-elastic-agent.htm)