{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/602","repository_url":"https://api.github.com/repos/kubernetes/kube-state-metrics","labels_url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/602/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/602/comments","events_url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/602/events","html_url":"https://github.com/kubernetes/kube-state-metrics/issues/602","id":385899733,"node_id":"MDU6SXNzdWUzODU4OTk3MzM=","number":602,"title":"[feature] calculation of job runtime","user":{"login":"sstarcher","id":3778974,"node_id":"MDQ6VXNlcjM3Nzg5NzQ=","avatar_url":"https://avatars0.githubusercontent.com/u/3778974?v=4","gravatar_id":"","url":"https://api.github.com/users/sstarcher","html_url":"https://github.com/sstarcher","followers_url":"https://api.github.com/users/sstarcher/followers","following_url":"https://api.github.com/users/sstarcher/following{/other_user}","gists_url":"https://api.github.com/users/sstarcher/gists{/gist_id}","starred_url":"https://api.github.com/users/sstarcher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sstarcher/subscriptions","organizations_url":"https://api.github.com/users/sstarcher/orgs","repos_url":"https://api.github.com/users/sstarcher/repos","events_url":"https://api.github.com/users/sstarcher/events{/privacy}","received_events_url":"https://api.github.com/users/sstarcher/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-11-29T19:52:24Z","updated_at":"2018-11-30T07:57:46Z","closed_at":null,"author_association":"NONE","body":"Currently completion time and start time exist.  Is there any easy way to currently calculate runtime with those 2 metrics?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/comments/443122010","html_url":"https://github.com/kubernetes/kube-state-metrics/issues/602#issuecomment-443122010","issue_url":"https://api.github.com/repos/kubernetes/kube-state-metrics/issues/602","id":443122010,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0MzEyMjAxMA==","user":{"login":"brancz","id":4546722,"node_id":"MDQ6VXNlcjQ1NDY3MjI=","avatar_url":"https://avatars3.githubusercontent.com/u/4546722?v=4","gravatar_id":"","url":"https://api.github.com/users/brancz","html_url":"https://github.com/brancz","followers_url":"https://api.github.com/users/brancz/followers","following_url":"https://api.github.com/users/brancz/following{/other_user}","gists_url":"https://api.github.com/users/brancz/gists{/gist_id}","starred_url":"https://api.github.com/users/brancz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brancz/subscriptions","organizations_url":"https://api.github.com/users/brancz/orgs","repos_url":"https://api.github.com/users/brancz/repos","events_url":"https://api.github.com/users/brancz/events{/privacy}","received_events_url":"https://api.github.com/users/brancz/received_events","type":"User","site_admin":false},"created_at":"2018-11-30T07:57:46Z","updated_at":"2018-11-30T07:57:46Z","author_association":"MEMBER","body":"kube-state-metrics fundamentally doesn't perform aggregations, it can only expose what the kubernetes object has in terms of information and turn exactly that into a metric. Generally that type of metric sounds like it would make sense as a histogram or summary, however the histogram would need to have chosen buckets and the summary would not be aggregatable. I think you're best off writing a new component that listens to job events and aggregates them by their runtime."}}
{"actor":{"display_login":"brancz"}}