You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How are you running this tool? Through docker or directly running on a server? Can you check if you can hit the url? Sometimes, if using docker, it can have a different dns configuration and it can't resolve your URL, especially if it's internal.
Hey,i always become this error:
URL unavailable
INFO [2019-07-11 17:04:03,217] cachet_url_monitor.configuration.Configuration - Monitoring URL: GET https://example.de/ INFO [2019-07-11 17:04:03,217] cachet_url_monitor.configuration.Configuration - Registered expectation: 'HTTP status range: (200, 300)' INFO [2019-07-11 17:04:03,217] cachet_url_monitor.scheduler.Scheduler - Registering action CREATE_INCIDENT INFO [2019-07-11 17:04:03,217] cachet_url_monitor.scheduler.Scheduler - Registering action UPDATE_STATUS INFO [2019-07-11 17:04:03,217] cachet_url_monitor.scheduler.Scheduler - Starting monitor agent... WARNING [2019-07-11 17:04:33,245] cachet_url_monitor.configuration.Configuration - Request timed out INFO [2019-07-11 17:04:33,245] cachet_url_monitor.configuration.Configuration - Failure #1 with threshold set to 0 INFO [2019-07-11 17:04:33,380] cachet_url_monitor.configuration.Configuration - Incident uploaded, API unhealthy: component status [2], message: "Request timed out"
My config is:
endpoint: url: https://example.de/ method: GET #header: #SOME-HEADER: SOME-VALUE timeout: 0.01 expectation: - type: HTTP_STATUS status_range: 200-300 #- type: LATENCY # threshold: 15 #- type: REGEX # regex: '.*(<body).*' allowed_fails: 0 cachet: api_url: https://status.example.de/api/v1 token: my_token component_id: 1 metric_id: 1 action: - CREATE_INCIDENT - UPDATE_STATUS public_incidents: true latency_unit: s frequency: 30
Edited url to example.de, dont post my real url here, also my token ;)
So what i am do wrong?
The text was updated successfully, but these errors were encountered: