{"action":"opened","issue":{"url":"https://api.github.com/repos/scylladb/scylla/issues/1641","repository_url":"https://api.github.com/repos/scylladb/scylla","labels_url":"https://api.github.com/repos/scylladb/scylla/issues/1641/labels{/name}","comments_url":"https://api.github.com/repos/scylladb/scylla/issues/1641/comments","events_url":"https://api.github.com/repos/scylladb/scylla/issues/1641/events","html_url":"https://github.com/scylladb/scylla/issues/1641","id":174795779,"number":1641,"title":"Add counter for writes blocked due to dirty memory","user":{"login":"tgrabiec","id":283695,"avatar_url":"https://avatars.githubusercontent.com/u/283695?v=3","gravatar_id":"","url":"https://api.github.com/users/tgrabiec","html_url":"https://github.com/tgrabiec","followers_url":"https://api.github.com/users/tgrabiec/followers","following_url":"https://api.github.com/users/tgrabiec/following{/other_user}","gists_url":"https://api.github.com/users/tgrabiec/gists{/gist_id}","starred_url":"https://api.github.com/users/tgrabiec/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tgrabiec/subscriptions","organizations_url":"https://api.github.com/users/tgrabiec/orgs","repos_url":"https://api.github.com/users/tgrabiec/repos","events_url":"https://api.github.com/users/tgrabiec/events{/privacy}","received_events_url":"https://api.github.com/users/tgrabiec/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/scylladb/scylla/labels/monitoring-tracing","name":"monitoring-tracing","color":"fbca04"}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-09-02T16:12:55Z","updated_at":"2016-09-02T16:12:55Z","closed_at":null,"body":"We have `memory/bytes-dirty`, but it's not enough. It's a gauge, so we may not notice its high value if it hits the threshold between samplings. Even if it's high, it's not easy to tell how many requests got delayed because of that.\r\n\r\nA `total_operations` counter for each delayed request, similar to what we have for timeouts, would be useful. It could be easily aggregated per-node and per-cluster.\r\n\r\nConsider also adding a counter for queuing delay, similar to `delay` counters in io_queues, which could be correlated with latency graphs.\r\n\r\n"}}
{"actor":{"display_login":"tgrabiec"}}