I have setup heartbeat to monitor kibana instance running in the same namespace (kubernetes) with following config
- type: http
enabled: true
name: "kibana"
tags: ["kibana"]
fields:
env: production
schedule: '@every 5s'
urls: ["http://kibana:5601"]
ipv4: true
ipv6: true
mode: any
timeout: 20s
check.request.method: "GET"
check.response.status: [200]
But this check doesn't passes. This is how it shows always
But I am able to curl http://kibana:5601 from heartbeat pods, here is the sample.
$ curl -v http://kibana:5601
* About to connect() to kibana port 5601 (#0)
* Trying 192.30.240.53...
* Connected to kibana (192.30.240.53) port 5601 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.29.0
> Host: kibana:5601
> Accept: */*
>
< HTTP/1.1 302 Found
< location: /spaces/enter
< kbn-name: kibana.example.com
< kbn-license-sig: 3f7bcc39e99265eb9150fe74242370b9b4bca5f1e6e9048b5193b88a1acea11b
< kbn-xpack-sig: 0213ac89bd6c118858950458439d872f
< cache-control: private, no-cache, no-store, must-revalidate
< content-length: 0
< Date: Fri, 23 Oct 2020 13:30:13 GMT
< Connection: keep-alive
<
* Connection #0 to host kibana left intact
What I am missing here ?
similar check for elasticsearch works fine.