{"action":"created","issue":{"url":"https://api.github.com/repos/Yelp/sensu/issues/2","labels_url":"https://api.github.com/repos/Yelp/sensu/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/Yelp/sensu/issues/2/comments","events_url":"https://api.github.com/repos/Yelp/sensu/issues/2/events","html_url":"https://github.com/Yelp/sensu/issues/2","id":54949771,"number":2,"title":"Develop a concept of 'check staleness'","user":{"login":"hashbrowncipher","id":124699,"avatar_url":"https://avatars.githubusercontent.com/u/124699?v=3","gravatar_id":"","url":"https://api.github.com/users/hashbrowncipher","html_url":"https://github.com/hashbrowncipher","followers_url":"https://api.github.com/users/hashbrowncipher/followers","following_url":"https://api.github.com/users/hashbrowncipher/following{/other_user}","gists_url":"https://api.github.com/users/hashbrowncipher/gists{/gist_id}","starred_url":"https://api.github.com/users/hashbrowncipher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hashbrowncipher/subscriptions","organizations_url":"https://api.github.com/users/hashbrowncipher/orgs","repos_url":"https://api.github.com/users/hashbrowncipher/repos","events_url":"https://api.github.com/users/hashbrowncipher/events{/privacy}","received_events_url":"https://api.github.com/users/hashbrowncipher/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-01-20T22:28:20Z","updated_at":"2015-01-26T19:28:13Z","closed_at":null,"body":"Right now, there is no way for a standalone check to become CRITICAL if no event is received for more than a defined period of time.  Creating such functionality would allow us to replace Nagios passive checks with masqueraded Sensu checks, and simplify the solution to #1."},"comment":{"url":"https://api.github.com/repos/Yelp/sensu/issues/comments/71521364","html_url":"https://github.com/Yelp/sensu/issues/2#issuecomment-71521364","issue_url":"https://api.github.com/repos/Yelp/sensu/issues/2","id":71521364,"user":{"login":"portertech","id":149630,"avatar_url":"https://avatars.githubusercontent.com/u/149630?v=3","gravatar_id":"","url":"https://api.github.com/users/portertech","html_url":"https://github.com/portertech","followers_url":"https://api.github.com/users/portertech/followers","following_url":"https://api.github.com/users/portertech/following{/other_user}","gists_url":"https://api.github.com/users/portertech/gists{/gist_id}","starred_url":"https://api.github.com/users/portertech/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/portertech/subscriptions","organizations_url":"https://api.github.com/users/portertech/orgs","repos_url":"https://api.github.com/users/portertech/repos","events_url":"https://api.github.com/users/portertech/events{/privacy}","received_events_url":"https://api.github.com/users/portertech/received_events","type":"User","site_admin":false},"created_at":"2015-01-26T19:28:13Z","updated_at":"2015-01-26T19:28:13Z","body":"@roobert all check results are \"transmitted\" by client, as that's how events are resolved etc. Sensu does not store OK results to reduce the ammount of data stored, for Sensu's concern has always been in what's broken, while allowing users to send that OK data elsewhere (that can effectively present it). Green light dashboards do not scale and most of the time the information users want is best stored in a time series database, eg. measurments. I'm curious if we can change how the last execution timestamp is stored, tack on the run interval, so that we can detect stale checks w/o making fundamental changes. Thoughts?"}}