Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quick question about the timeout config... #53

Closed
haydenjames opened this issue Jan 18, 2017 · 1 comment
Closed

Quick question about the timeout config... #53

haydenjames opened this issue Jan 18, 2017 · 1 comment

Comments

@haydenjames
Copy link

haydenjames commented Jan 18, 2017

Here's my current config:

`{
  "api_url": "http://status.mysite.com/api/v1",
  "api_token": "xxxxx",
  "insecure_api": true,
  "monitors": [
    {
      "name": "mysite",
      "url":  "http://mysite.com/ping",
      "threshold": 80,
      "component_id": 3,
      "metric_id": 4,
      "interval": 30,
      "timeout": 25,
      "expected_status_code": 200
    }
  ]
}

If I set "timeout": 60, instead of 25. Will that overlap (interval is 30) cause issues with monitor? Will it wait for that check to timeout until next check or will the interval of 30 reset?

For my timeout I would like 60 seconds but when I set interval to 120 and set cacht's:
"How many minutes of threshold between metric point?" to 5

The graph still shows 1 min intervals. The metric never obey the minute setting of 300 seconds.

So Hoping to use 30 second interval and longer timeout.

Possible?

@matejkramny
Copy link
Member

It's not possible to have a timeout which is greater than the interval.

The metrics may be a cachet bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants