Hi, I'm facing an issue where heartbeat 7.5 reports a different response code (500) value than cUrl (302) reports on the same target URL I believe the heartbeat can me mimicked through curl -Iv. Below the heartbeat configuration in monitor.d, the corresponding response doc and curl output. What cou…

Ah, makes sense. Thanks for letting us know it's been resolved! So, to summarize the issue was that the service returned a 500 for the heartbeat default user agent (which is the go user agent). This should (probably?) cease to be an issue in 7.6.0 with the new default agent. It really depends on h…

system (system) Closed January 13, 2020, 7:34pm 10

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

Topic		Replies	Views
After redirect connection reset by peer Beats heartbeat	3	620	May 28, 2020
Heartbeat HTTP pings fails with 403 Beats heartbeat	2	1226	March 28, 2022
Wrong response code sent by heartbeat Beats heartbeat	2	401	February 9, 2022
Heartbeat http not providing any ping result Beats heartbeat	2	359	October 18, 2021
Heartbeat showing application as down even when its up Beats heartbeat	10	878	July 18, 2019

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Inconsistent response code from heartbeat and curl command from same machine

Related topics