Make sense, marked as approved. Feel free to submit a PR if you're interested in the change otherwise, I'll eventually get around to it.

I'm going to take a shot at this if no one else is already working on it.

@fbartels just FYI you can override this on a per check basis.

http:
  https://www.google.com:
    status: 200
    allow-insecure: false
    no-follow-redirects: false
    timeout: 1000
    username: ""
    password: ""
    ca-file: ""
    cert-file: ""
    key-file: ""
    proxy: ""
    skip: false
    method: GET
    request-headers:
        - 'user-agent: whatever/you/want/goes/here'

@catdevman thanks or the hint regarding request-headers. I did miss that setting custom headers is already possible in http checks. I can confirm that this works as a workaround until goss sets a proper user-agent.