{"action":"opened","issue":{"url":"https://api.github.com/repos/eversC/inspectr/issues/67","repository_url":"https://api.github.com/repos/eversC/inspectr","labels_url":"https://api.github.com/repos/eversC/inspectr/issues/67/labels{/name}","comments_url":"https://api.github.com/repos/eversC/inspectr/issues/67/comments","events_url":"https://api.github.com/repos/eversC/inspectr/issues/67/events","html_url":"https://github.com/eversC/inspectr/issues/67","id":280148107,"number":67,"title":"report on tls certs nearing expiration time","user":{"login":"eversC","id":19394586,"avatar_url":"https://avatars2.githubusercontent.com/u/19394586?v=4","gravatar_id":"","url":"https://api.github.com/users/eversC","html_url":"https://github.com/eversC","followers_url":"https://api.github.com/users/eversC/followers","following_url":"https://api.github.com/users/eversC/following{/other_user}","gists_url":"https://api.github.com/users/eversC/gists{/gist_id}","starred_url":"https://api.github.com/users/eversC/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eversC/subscriptions","organizations_url":"https://api.github.com/users/eversC/orgs","repos_url":"https://api.github.com/users/eversC/repos","events_url":"https://api.github.com/users/eversC/events{/privacy}","received_events_url":"https://api.github.com/users/eversC/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-12-07T14:25:21Z","updated_at":"2017-12-07T14:25:21Z","closed_at":null,"author_association":"OWNER","body":"need to think about what's deemed to be \"near\" expiration time -- should probably have that configurable\r\n\r\nmaintaining a cache of what's previously been reported would be nice (like we do with image upgrades) to prevent unnecessary noise. Might need \"banding\" with varying levels of cache expiries (people will want to be annoyed by inspectr a little more if their cert is due to expire tomorrow, as opposed to in a months' time...)\r\n\r\nif the cert is letsencrypt, maybe we should hassle people less, due to automation?\r\n\r\nmaybe, now the prom endpoint is being exposed, we want to set some values (?)\r\n\r\nalso alert on freshly renewed certs (most helpful if using letsencrypt)\r\n\r\nperhaps there should be a way of telling inspectr where to look for the certs. Some people may not want to grant it access to look at ALL secrets.\r\n\r\nA LOT to think about here!!"}}
{"actor":{"display_login":"eversC"}}