{"action":"created","issue":{"url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/27","repository_url":"https://api.github.com/repos/F43nd1r/Acrarium","labels_url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/27/labels{/name}","comments_url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/27/comments","events_url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/27/events","html_url":"https://github.com/F43nd1r/Acrarium/issues/27","id":370630855,"node_id":"MDU6SXNzdWUzNzA2MzA4NTU=","number":27,"title":"Emails on New Issues","user":{"login":"wbrawner","id":11827417,"node_id":"MDQ6VXNlcjExODI3NDE3","avatar_url":"https://avatars2.githubusercontent.com/u/11827417?v=4","gravatar_id":"","url":"https://api.github.com/users/wbrawner","html_url":"https://github.com/wbrawner","followers_url":"https://api.github.com/users/wbrawner/followers","following_url":"https://api.github.com/users/wbrawner/following{/other_user}","gists_url":"https://api.github.com/users/wbrawner/gists{/gist_id}","starred_url":"https://api.github.com/users/wbrawner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wbrawner/subscriptions","organizations_url":"https://api.github.com/users/wbrawner/orgs","repos_url":"https://api.github.com/users/wbrawner/repos","events_url":"https://api.github.com/users/wbrawner/events{/privacy}","received_events_url":"https://api.github.com/users/wbrawner/received_events","type":"User","site_admin":false},"labels":[{"id":607276250,"node_id":"MDU6TGFiZWw2MDcyNzYyNTA=","url":"https://api.github.com/repos/F43nd1r/Acrarium/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-10-16T14:07:23Z","updated_at":"2018-12-07T22:20:53Z","closed_at":null,"author_association":"NONE","body":"It would be nice to be able to configure email settings to get alerts from Acrarium. I can think of a few use cases where this might be useful:\r\n\r\n- a new issue is reported\r\n- an issue marked as resolved shows up in a new release (a regression)\r\n- a massive number of issues suddenly are reported (e.g. 20% more than usual)\r\n- a weekly summary of the top issues"},"comment":{"url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/comments/445383738","html_url":"https://github.com/F43nd1r/Acrarium/issues/27#issuecomment-445383738","issue_url":"https://api.github.com/repos/F43nd1r/Acrarium/issues/27","id":445383738,"node_id":"MDEyOklzc3VlQ29tbWVudDQ0NTM4MzczOA==","user":{"login":"wbrawner","id":11827417,"node_id":"MDQ6VXNlcjExODI3NDE3","avatar_url":"https://avatars2.githubusercontent.com/u/11827417?v=4","gravatar_id":"","url":"https://api.github.com/users/wbrawner","html_url":"https://github.com/wbrawner","followers_url":"https://api.github.com/users/wbrawner/followers","following_url":"https://api.github.com/users/wbrawner/following{/other_user}","gists_url":"https://api.github.com/users/wbrawner/gists{/gist_id}","starred_url":"https://api.github.com/users/wbrawner/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wbrawner/subscriptions","organizations_url":"https://api.github.com/users/wbrawner/orgs","repos_url":"https://api.github.com/users/wbrawner/repos","events_url":"https://api.github.com/users/wbrawner/events{/privacy}","received_events_url":"https://api.github.com/users/wbrawner/received_events","type":"User","site_admin":false},"created_at":"2018-12-07T22:20:53Z","updated_at":"2018-12-07T22:20:53Z","author_association":"NONE","body":"> > a new issue is reported\r\n> \r\n> This one is easy. However it can get spammy really fast, so I don't think many people need this.\r\n\r\nRight, my idea was that if an issue that hasn't been seen before (based on the hash of the stacktrace or something) is reported, _then_ it can be emailed to you. I don't want an email for every time an error is reported either, just if it's something that Acrarium hasn't seen before.\r\n\r\n> > an issue marked as resolved shows up in a new release (a regression)\r\n>\r\n> I'm not sure the current database structure supports this. A bug can have stacktraces from multiple versions, and I don't know in which version it was marked as solved.\r\n\r\nYeah, it would most likely require not only marking an issue as solved but solved as of x version. Didn't know how big of a change it would be but I figured I'd suggest it anyways\r\n\r\n> > a massive number of issues suddenly are reported (e.g. 20% more than usual)\r\n>\r\n> It is quite hard to define what is 'usual'. E.g. if I compared the last hour to the 5 hours before that, there might just be more reports because it was night. If you have nice ideas how to approach this, let me know.\r\n\r\nI don't think an hourly check would be good, maybe a daily check at most? So you could compare the average number of issues over the past 7 days, and see if the issues reported within the last 24 hours more or less align with the averages of the past 7 days. I.e. if you see that you're getting around 50 issues per day for the past 7 days, and suddenly within the last 24 hours you have 100 new issues, that should trigger an alert that maybe something is wrong. \r\n\r\n> a weekly summary of the top issues\r\n>\r\n> Weekly summary is easy. How would you define 'top issues'?\r\n\r\nFor top issues I would just say the 5 most commonly reported in that week. If there were no issues reported in the week, then it could also send out a congratulatory message that everything appears to be working correctly. "}}
{"actor":{"display_login":"wbrawner"}}