{"action":"opened","issue":{"url":"https://api.github.com/repos/linkedin/Burrow/issues/223","repository_url":"https://api.github.com/repos/linkedin/Burrow","labels_url":"https://api.github.com/repos/linkedin/Burrow/issues/223/labels{/name}","comments_url":"https://api.github.com/repos/linkedin/Burrow/issues/223/comments","events_url":"https://api.github.com/repos/linkedin/Burrow/issues/223/events","html_url":"https://github.com/linkedin/Burrow/issues/223","id":230070438,"number":223,"title":"Consumer status WARN when lag is very low","user":{"login":"kylemurph","id":359977,"avatar_url":"https://avatars0.githubusercontent.com/u/359977?v=3","gravatar_id":"","url":"https://api.github.com/users/kylemurph","html_url":"https://github.com/kylemurph","followers_url":"https://api.github.com/users/kylemurph/followers","following_url":"https://api.github.com/users/kylemurph/following{/other_user}","gists_url":"https://api.github.com/users/kylemurph/gists{/gist_id}","starred_url":"https://api.github.com/users/kylemurph/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kylemurph/subscriptions","organizations_url":"https://api.github.com/users/kylemurph/orgs","repos_url":"https://api.github.com/users/kylemurph/repos","events_url":"https://api.github.com/users/kylemurph/events{/privacy}","received_events_url":"https://api.github.com/users/kylemurph/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-05-19T19:36:06Z","updated_at":"2017-05-19T19:36:06Z","closed_at":null,"body":"According to the consumer lag evaluation rules - https://github.com/linkedin/Burrow/wiki/Consumer-Lag-Evaluation-Rules, whenever lag increases, the status is set to WARN:\r\n\r\n> 3. If the consumer offsets are increasing over the window, but the lag either stays the same or increases between every pair of offsets, the consumer is in a WARNING state. This means that the consumer is slow, and is falling behind.\r\n\r\nIs there a way to set a threshold for lag in addition to this, my issue is that we trigger alerts on WARNs, but lag is very low - around 200, and clears quickly, whereas we might only want to get a WARN when lag is > 1K or so:\r\n\r\n```\r\n{\r\n\"error\": false,\r\n\"message\": \"consumer group status returned\",\r\n\"status\": {\r\n\"cluster\": \"local\",\r\n\"group\": \"CONSUMER_GROUP\",\r\n\"status\": \"WARN\",\r\n\"complete\": true,\r\n\"partitions\": [\r\n{\r\n\"topic\": \"TOPIC\",\r\n\"partition\": 14,\r\n\"status\": \"WARN\",\r\n\"start\": {\r\n\"offset\": 112878341,\r\n\"timestamp\": 1495220705275,\r\n\"lag\": 11\r\n},\r\n\"end\": {\r\n\"offset\": 112882841,\r\n\"timestamp\": 1495221784466,\r\n\"lag\": 145\r\n}\r\n},\r\n{\r\n\"topic\": \"TOPIC\",\r\n\"partition\": 23,\r\n\"status\": \"WARN\",\r\n\"start\": {\r\n\"offset\": 112878287,\r\n\"timestamp\": 1495220705279,\r\n\"lag\": 51\r\n},\r\n\"end\": {\r\n\"offset\": 112882787,\r\n\"timestamp\": 1495221784464,\r\n\"lag\": 185\r\n}\r\n}\r\n```\r\n"}}
{"actor":{"display_login":"kylemurph"}}