After redirect connection reset by peer

Elastic Stack Beats
1

Hi,

I use heartbeat to monitor an URL, that is redirected to another.

The configuration is:

    - type: http
      urls: ["https://www.123-usability.de"]
      max_redirects: 20
      ssl.verification_mode: none
      check.response.status: 200
      # Configure task schedule
      schedule: '@every 10m'
      name: "TIC_URL_Check-www.123-usability.de"

The domain is seen as down and I get the following error:

Get https://www.t-systems-mms.com/: read tcp 192.168.58.70:54188->3.124.154.62:443: read: connection reset by peer

I tried it also with the option headers: "'User-Agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:75.0) Gecko/20100101 Firefox/75.0'", to no avail.

What can I do, is there a special option I missed?

Best regards,
Robert

2

Hmmm, I just tried that config, and it worked for me. That said, I've noticed it's somewhat slow, and takes a couple seconds to work. Is there perhaps an issue with the site?

As an aside, you should always set the id attribute alongside name.

I've placed a sample document below:

{
  "@timestamp": "2020-04-29T22:07:40.156Z",
  "@metadata": {
    "beat": "heartbeat",
    "type": "_doc",
    "version": "7.6.2"
  },
  "summary": {
    "up": 1,
    "down": 0
  },
  "event": {
    "dataset": "uptime"
  },
  "ecs": {
    "version": "1.4.0"
  },
  "agent": {
    "hostname": "x1e",
    "id": "e29b8d00-70ba-4e55-ad20-fc81591dca38",
    "version": "7.6.2",
    "type": "heartbeat",
    "ephemeral_id": "09dd1c46-9b38-4457-bc5e-11d9d24cc82d"
  },
  "observer": {
    "hostname": "x1e"
  },
  "http": {
    "response": {
      "redirects": [
        "https://www.t-systems-mms.com/"
      ],
      "status_code": 200,
      "body": {
        "hash": "eb9c35d45a431f6ab3acf7cc05aa71dc98cbfeacf281d5efb52784bf042d4554",
        "bytes": 60909
      }
    },
    "rtt": {
      "total": {
        "us": 2300477
      }
    }
  },
  "url": {
    "scheme": "https",
    "domain": "www.123-usability.de",
    "port": 443,
    "full": "https://www.123-usability.de"
  },
  "monitor": {
    "check_group": "d7972a2a-8a65-11ea-93b3-482ae353ebb8",
    "status": "up",
    "duration": {
      "us": 2300499
    },
    "id": "auto-http-0X1CA1EDBEBF95D8E",
    "name": "TIC_URL_Check-www.123-usability.de",
    "type": "http",
    "timespan": {
      "gte": "2020-04-29T22:07:40.156Z",
      "lt": "2020-04-29T22:17:40.156Z"
    }
  }
}
3

Hi,

The problem is solved. The solution has nothing to do with heartbeat.
Thank you for your effort.

Best regards,
Robert