{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/22421","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/22421/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/22421/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/22421/events","html_url":"https://github.com/kubernetes/kubernetes/issues/22421","id":138122471,"number":22421,"title":"Add metric for client rate limiter saturation (for all clients)","user":{"login":"gmarek","id":1703842,"avatar_url":"https://avatars.githubusercontent.com/u/1703842?v=3","gravatar_id":"","url":"https://api.github.com/users/gmarek","html_url":"https://github.com/gmarek","followers_url":"https://api.github.com/users/gmarek/followers","following_url":"https://api.github.com/users/gmarek/following{/other_user}","gists_url":"https://api.github.com/users/gmarek/gists{/gist_id}","starred_url":"https://api.github.com/users/gmarek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gmarek/subscriptions","organizations_url":"https://api.github.com/users/gmarek/orgs","repos_url":"https://api.github.com/users/gmarek/repos","events_url":"https://api.github.com/users/gmarek/events{/privacy}","received_events_url":"https://api.github.com/users/gmarek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/monitoring","name":"area/monitoring","color":"fef2c0"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/area/performance","name":"area/performance","color":"d4c5f9"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-03T09:19:28Z","updated_at":"2016-03-03T09:23:44Z","closed_at":null,"body":"As we found out recent regression was caused by hitting rate limit in one of components (#22340). It's not the first time it hits us, so we really need to make sure it will be easier to debug in future. To do this we can add a per-client prometheus metric exposing rate limiter saturation level. cc @smarterclayton @lavalamp @wojtek-t @fgrzadkowski @davidopp \r\n\r\nI see two options. Either make client rate limiter injectable, and let the client owner handle exposing and updating the metrics, or let the client itself do all of this (i.e. register metric and have a go-routine that periodically updates it). I'm leaning towards the first option."},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/191673828","html_url":"https://github.com/kubernetes/kubernetes/issues/22421#issuecomment-191673828","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/22421","id":191673828,"user":{"login":"wojtek-t","id":10743879,"avatar_url":"https://avatars.githubusercontent.com/u/10743879?v=3","gravatar_id":"","url":"https://api.github.com/users/wojtek-t","html_url":"https://github.com/wojtek-t","followers_url":"https://api.github.com/users/wojtek-t/followers","following_url":"https://api.github.com/users/wojtek-t/following{/other_user}","gists_url":"https://api.github.com/users/wojtek-t/gists{/gist_id}","starred_url":"https://api.github.com/users/wojtek-t/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wojtek-t/subscriptions","organizations_url":"https://api.github.com/users/wojtek-t/orgs","repos_url":"https://api.github.com/users/wojtek-t/repos","events_url":"https://api.github.com/users/wojtek-t/events{/privacy}","received_events_url":"https://api.github.com/users/wojtek-t/received_events","type":"User","site_admin":false},"created_at":"2016-03-03T09:23:44Z","updated_at":"2016-03-03T09:23:44Z","body":"@kubernetes/sig-scalability "}}