Heartbeat http monitor is not sending headers

[marvnz (Martin Arndt)]

I have configured the following http monitor:

heartbeat.monitors:
- type: "http"
  urls: ["http://elasticsearch-dev-master.dev-common-cache.svc.cluster.local:9200","https://dev-common-cache.gubbins.bobbins","http://10.10.10.10:33101/"]
  schedule: "@every 10s"
  check.request.method: "GET"
  check.request.headers:
    HOST: 'dev-common-cache.gubbins.bobbins'
  check.response.body: "You Know, for Search"

These 3 urls all point to the same elasticsearch cluster, but just being reached through different network endpoints to try to establish they are all working.

However I don't think the headers are being sent through as the endpoint that goes through the nginx-ingress controller is not working as it requires that header to route the request. So my question is have I configured the http monitor correctly? Also I have enabled debug logging, but that doesn't show what the request looks like.

[ruflin]

At first sight, your config looks correct. I stumbled over the HOST in upper-case. I assume that is intended?

As you already run it with the debug log, any chance you could share it?

[marvnz (Martin Arndt)]

I have tried it lower case and in single quotes, but always the same http 404.

I can curl the ingress controller with the HOST: header and it works, but heartbeat can not successfully send the header so it keeps getting a validate 404 Not Found error as you can see in the screenshot attached.

[martinr_ubi (Martin R.)]

Hi @marvnz ,

This is a known bug/undocumented limitation of heartbeat < v6.7.0.
Specifically, the "host" header is ignored, it comes from GO, see below.

Originally reported:

[HTTP check] Override Host header

Hello, I have troubles overriding the Host header. I want to test individually: My CDN My varnish My backend To do that i need to check the IP with a custom Header, if i had to script it i would use Curl: curl -I -H "Host:my_superb_domain_name.com" http://IPCDN/myasset.json curl -I -H "Host:my_superb_domain_name.com" http://IPvarnish/myasset.json curl -I -H "Host:my_superb_domain_name.com" http://IPbackend/myasset.json So i tried to do something like that: - type: http urls: ["htt…

Issue:

[Heartbeat]Permit Host header override

fix: (commit and pull)

Allow the Host header to be overriden (fixes #9376) (#9516)

Allow the Host header to be overriden (fixes #9376)

Backport to 6.7.0:

Cherry-pick #9516 to 6.x: Allow the Host header to be overriden (fixes #9376)

I myself didn't figure it out until I pointed heartbeat to a local netcat and figured that only the "host" header was silently ignored by heartbeat.
nc -kl 8888

My struggle:

Heartbeat bug with fix in 7.x, if no backport... doc fix in 6.x?

Hi, I lost some time investigating why Heartbeat 6.6.2 (lastest stable) was not respecting the "Host" http header I was configuring in an HTTP monitor. I was using exactly what the doc was saying, etc. Turns out when I understood the issue was specific to a specific header.. "Host" and not to all http headers. I looked for a known or unknown bug and found: Question is: If this fix is not scheduled to be backported to older heartbeat, I would recommend a documentation fix for older versi…

Instant relief with 6.7.

Hoping this helps,

Martin