Heartbeat showing application as down even when its up


I have an application URL 1 that redirects to a different URL 2. From browser when I hit URL 1 , it redirects me to URL 2 and in network I can see that URL 1 returns response code as 302 as its redirecting to URL 2. But when I monitor URL 1 using heartbeat, heartbeat is showing as 404. Please assist !

NOTE: I was able to ping the host of URL 1 as well from CMD prompt.

Can you access the host via curl? If it's a 404 there's something about the way the app is reacting to heartbeat that is different. It could also be an issue where the URL needs you to be logged in or have a special header.

Yes, I'm able to access the URL via curl and getting 302 as expected. Getting 404 only via heartbeat.

@Andrew_Cholakian1 Can you please assist with this !

I suspect you'll need to debug this from the application side. There must be some logic in the application that is causing it to return a 404 due to some input parameter.

Since I'm not getting any issue when I do curl, do you think it's still an issue with the application that's making it to return 404 ?

Yes. Some sites (including discuss.elastic.co) block unexpected user agents like heartbeat.

At any rate it's impossible to debug without seeing both sides of the connection. If you do find that is definitively a heartbeat bug please let us know.

thanks for the info.

I will try to debug with the application team who owns that URL and will provide the feedback.

FYI.. As an alternative, I tried http_poller input plugin in Logstash and still facing the similar issue.

@sjabiulla, You can monitor the uptime in Kibana, have you tried that? It can tell if your application is up or down.

Could you please provide the exact user agent name that HeartBeat uses to check the URL's ?

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