{"action":"created","issue":{"url":"https://api.github.com/repos/apex/up/issues/592","repository_url":"https://api.github.com/repos/apex/up","labels_url":"https://api.github.com/repos/apex/up/issues/592/labels{/name}","comments_url":"https://api.github.com/repos/apex/up/issues/592/comments","events_url":"https://api.github.com/repos/apex/up/issues/592/events","html_url":"https://github.com/apex/up/issues/592","id":298122173,"number":592,"title":"is monitoring working?","user":{"login":"davidjnelson","id":381633,"avatar_url":"https://avatars2.githubusercontent.com/u/381633?v=4","gravatar_id":"","url":"https://api.github.com/users/davidjnelson","html_url":"https://github.com/davidjnelson","followers_url":"https://api.github.com/users/davidjnelson/followers","following_url":"https://api.github.com/users/davidjnelson/following{/other_user}","gists_url":"https://api.github.com/users/davidjnelson/gists{/gist_id}","starred_url":"https://api.github.com/users/davidjnelson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidjnelson/subscriptions","organizations_url":"https://api.github.com/users/davidjnelson/orgs","repos_url":"https://api.github.com/users/davidjnelson/repos","events_url":"https://api.github.com/users/davidjnelson/events{/privacy}","received_events_url":"https://api.github.com/users/davidjnelson/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-02-18T21:57:20Z","updated_at":"2018-02-20T01:43:24Z","closed_at":null,"author_association":"NONE","body":"## Prerequisites\r\n\r\n* [x] I am running the latest version. (`up upgrade`)\r\n* [x] I searched to see if the issue already exists.\r\n* [x] I inspected the verbose debug output with the `-v, --verbose` flag.\r\n* [x] Are you an Up Pro subscriber?\r\n\r\n## Description\r\n\r\nI am not seeing alarm emails.  I checked my spam folder.\r\n\r\n## Steps to Reproduce\r\n\r\nIn my up.json I have:\r\n\r\n`\r\n\r\n\"actions\": [\r\n    {\r\n      \"name\": \"email.backend\",\r\n      \"type\": \"email\",\r\n      \"emails\": [\"my-real@email.host\"]\r\n\t\t}\r\n\t],\r\n\t\"alerts\": [\r\n    {\r\n      \"metric\": \"http.count\",\r\n      \"statistic\": \"sum\",\r\n      \"threshold\": 100,\r\n      \"action\": \"email.backend\"\r\n    },\r\n    {\r\n      \"metric\": \"http.5xx\",\r\n      \"statistic\": \"sum\",\r\n      \"threshold\": 1,\r\n      \"period\": \"1m\",\r\n      \"action\": \"email.backend\"\r\n    },\r\n    {\r\n      \"metric\": \"http.4xx\",\r\n      \"statistic\": \"sum\",\r\n      \"threshold\": 50,\r\n      \"period\": \"5m\",\r\n      \"action\": \"email.backend\"\r\n    },\r\n    {\r\n      \"metric\": \"http.latency\",\r\n      \"statistic\": \"avg\",\r\n      \"threshold\": 1000,\r\n      \"period\": \"5m\",\r\n      \"action\": \"email.backend\",\r\n      \"description\": \"Large traffic spike\"\r\n\t\t}\r\n\t]\r\n\r\n`\r\n\r\nI've run `up stack plan -v` and `up stack apply -v`, as well as `up deploy staging -v` and `up deploy production -v`.\r\n\r\nI am using cloudflare for dns with the cdn currently turned off.\r\n\r\nI threw load at it for 10 minutes to see if I got alerts:\r\n\r\n`wrk -d 5s -t 4 -c 1000 -d 10m --latency <myprodsiteurl>`\r\n\r\nI did not get any alerts in my inbox or spam folder.\r\n\r\nWhen I ran the tests in #591 I did get a single alert email:\r\n\r\n`\r\n\r\nAlert Resolved\r\nThe http requests count sum of <appname> is no longer greater than 100 in the past minute from <region>.\r\n\r\n1 datapoint [15.0 (18/02/18 20:36:00)] was not greater than the threshold (100.0).\r\n\r\n`\r\n\r\nSo it looks like ses is sending emails to some extent, and my email is receiving from ses to some extent.\r\n\r\nIs my configuration right?  Thanks :-)\r\n\r\n## Love Up?\r\n\r\nya!!!"},"comment":{"url":"https://api.github.com/repos/apex/up/issues/comments/366843805","html_url":"https://github.com/apex/up/issues/592#issuecomment-366843805","issue_url":"https://api.github.com/repos/apex/up/issues/592","id":366843805,"user":{"login":"tj","id":25254,"avatar_url":"https://avatars2.githubusercontent.com/u/25254?v=4","gravatar_id":"","url":"https://api.github.com/users/tj","html_url":"https://github.com/tj","followers_url":"https://api.github.com/users/tj/followers","following_url":"https://api.github.com/users/tj/following{/other_user}","gists_url":"https://api.github.com/users/tj/gists{/gist_id}","starred_url":"https://api.github.com/users/tj/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tj/subscriptions","organizations_url":"https://api.github.com/users/tj/orgs","repos_url":"https://api.github.com/users/tj/repos","events_url":"https://api.github.com/users/tj/events{/privacy}","received_events_url":"https://api.github.com/users/tj/received_events","type":"User","site_admin":false},"created_at":"2018-02-20T01:43:24Z","updated_at":"2018-02-20T01:43:24Z","author_association":"OWNER","body":"Hmm from your `up stack plan` output in #591 it looks like they weren't added? There's a few `AWS::CloudWatch::Alarm` in there, maybe the `up stack apply` was rolled back? `up stack` should have those errors (if any) and say something like \"status: Stack update rolled back\""}}
{"actor":{"display_login":"tj"}}