{"action":"created","issue":{"url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/1","labels_url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/1/comments","events_url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/1/events","html_url":"https://github.com/tylrtrmbl/sentry-in-a-box/issues/1","id":23051483,"number":1,"title":"100% Celery - Runaway CPU","user":{"login":"tylrtrmbl","id":1058478,"avatar_url":"https://avatars.githubusercontent.com/u/1058478?v=3","gravatar_id":"","url":"https://api.github.com/users/tylrtrmbl","html_url":"https://github.com/tylrtrmbl","followers_url":"https://api.github.com/users/tylrtrmbl/followers","following_url":"https://api.github.com/users/tylrtrmbl/following{/other_user}","gists_url":"https://api.github.com/users/tylrtrmbl/gists{/gist_id}","starred_url":"https://api.github.com/users/tylrtrmbl/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tylrtrmbl/subscriptions","organizations_url":"https://api.github.com/users/tylrtrmbl/orgs","repos_url":"https://api.github.com/users/tylrtrmbl/repos","events_url":"https://api.github.com/users/tylrtrmbl/events{/privacy}","received_events_url":"https://api.github.com/users/tylrtrmbl/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2013-11-21T08:45:17Z","updated_at":"2015-02-23T21:04:40Z","closed_at":null,"body":"Every once in a while (every few days it seems) I get Celery workers who start running at 100% CPU. Then Linode tells me I'm probably doing something wrong.\r\n\r\nIt's happened twice now, so tracking down the root cause wouldn't be useless I think.\r\n"},"comment":{"url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/comments/75631351","html_url":"https://github.com/tylrtrmbl/sentry-in-a-box/issues/1#issuecomment-75631351","issue_url":"https://api.github.com/repos/tylrtrmbl/sentry-in-a-box/issues/1","id":75631351,"user":{"login":"dcramer","id":23610,"avatar_url":"https://avatars.githubusercontent.com/u/23610?v=3","gravatar_id":"","url":"https://api.github.com/users/dcramer","html_url":"https://github.com/dcramer","followers_url":"https://api.github.com/users/dcramer/followers","following_url":"https://api.github.com/users/dcramer/following{/other_user}","gists_url":"https://api.github.com/users/dcramer/gists{/gist_id}","starred_url":"https://api.github.com/users/dcramer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dcramer/subscriptions","organizations_url":"https://api.github.com/users/dcramer/orgs","repos_url":"https://api.github.com/users/dcramer/repos","events_url":"https://api.github.com/users/dcramer/events{/privacy}","received_events_url":"https://api.github.com/users/dcramer/received_events","type":"User","site_admin":false},"created_at":"2015-02-23T21:04:40Z","updated_at":"2015-02-23T21:04:40Z","body":"You may try running \"sentry worker -B -l INFO\" (specifically the -l INFO part)\r\n\r\nThis will give you more insight into what the workers are doing, but without metrics you won't be in a good spot, and with that in mind I dont think we've instrumented the open source Sentry."}}