Skip to content

Hardcoded timeout of 10 seconds causing false down alerts in slow website #11

Description

@neilbrookins

My websites typically take 5 to 11 seconds to load due to various reasons. Since this integration has hardcoded a 10 second client timeout it will report an outage every time the website takes 10.0001 seconds or longer to respond even though the website is up and working normally. Keep in mind the 10 seconds is including the DNS resolution delay that is out of control of the webserver entirely. If DNS takes 9 seconds and the website takes 1.1 seconds it will still report down even though 1.1 second response time is quite fast.

The solution is to make the timeout a configuration parameter that is configurable by the end user on a per URL basis; similar to how the feature for ssl checking is set per URL.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions