{"action":"created","issue":{"url":"https://api.github.com/repos/flapjack/flapjack/issues/866","labels_url":"https://api.github.com/repos/flapjack/flapjack/issues/866/labels{/name}","comments_url":"https://api.github.com/repos/flapjack/flapjack/issues/866/comments","events_url":"https://api.github.com/repos/flapjack/flapjack/issues/866/events","html_url":"https://github.com/flapjack/flapjack/issues/866","id":76173951,"number":866,"title":"1.6 RC1 and Pagerduty - incidents not being created on pagerduty","user":{"login":"jessereynolds","id":391439,"avatar_url":"https://avatars.githubusercontent.com/u/391439?v=3","gravatar_id":"","url":"https://api.github.com/users/jessereynolds","html_url":"https://github.com/jessereynolds","followers_url":"https://api.github.com/users/jessereynolds/followers","following_url":"https://api.github.com/users/jessereynolds/following{/other_user}","gists_url":"https://api.github.com/users/jessereynolds/gists{/gist_id}","starred_url":"https://api.github.com/users/jessereynolds/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessereynolds/subscriptions","organizations_url":"https://api.github.com/users/jessereynolds/orgs","repos_url":"https://api.github.com/users/jessereynolds/repos","events_url":"https://api.github.com/users/jessereynolds/events{/privacy}","received_events_url":"https://api.github.com/users/jessereynolds/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/flapjack/flapjack/labels/Bug","name":"Bug","color":"e10c02"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-05-14T00:22:09Z","updated_at":"2015-05-14T00:39:06Z","closed_at":null,"body":"Reported by qgriffith via the mailing list: \r\n\r\n> I just installed the 1.6 RC1 version to in order to test the pager duty token authentication fix.  I added my credentials for pager duty and triggered an alarm in Sensu to send over to flapjack. The alarm triggered, but the alert never got to pager duty.  I see this in the logs\r\n\r\n```\r\n2015-05-13T11:40:32.323910-07:00 [DEBUG] :: flapjack-pagerduty :: looking for acks in pagerduty for unack'd problems\r\n2015-05-13T11:40:32.325451-07:00 [DEBUG] :: flapjack-pagerduty :: found unacknowledged failing checks as follows: #<Flapjack::Data::EntityCheck:0x00000007191200>, #<Flapjack::Data::EntityCheck:0x00000007190580>, #<Flapjack::Data::EntityCheck:0x000000071978d0>\r\n```"},"comment":{"url":"https://api.github.com/repos/flapjack/flapjack/issues/comments/101865760","html_url":"https://github.com/flapjack/flapjack/issues/866#issuecomment-101865760","issue_url":"https://api.github.com/repos/flapjack/flapjack/issues/866","id":101865760,"user":{"login":"jessereynolds","id":391439,"avatar_url":"https://avatars.githubusercontent.com/u/391439?v=3","gravatar_id":"","url":"https://api.github.com/users/jessereynolds","html_url":"https://github.com/jessereynolds","followers_url":"https://api.github.com/users/jessereynolds/followers","following_url":"https://api.github.com/users/jessereynolds/following{/other_user}","gists_url":"https://api.github.com/users/jessereynolds/gists{/gist_id}","starred_url":"https://api.github.com/users/jessereynolds/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jessereynolds/subscriptions","organizations_url":"https://api.github.com/users/jessereynolds/orgs","repos_url":"https://api.github.com/users/jessereynolds/repos","events_url":"https://api.github.com/users/jessereynolds/events{/privacy}","received_events_url":"https://api.github.com/users/jessereynolds/received_events","type":"User","site_admin":false},"created_at":"2015-05-14T00:39:06Z","updated_at":"2015-05-14T00:39:06Z","body":"The log lines you've included are to do with retrieving of acknowledgements. It looks like there's a bug with the debug logging, but it is not affecting the functionality for me. That is, incident creation in pagerduty is working, as is acknowledgement retrieval. Eg I see lines like this:\r\n\r\n```\r\n2015-05-14T09:57:00.054347+09:30 [DEBUG] :: flapjack-pagerduty :: found unacknowledged failing checks as follows: #<Flapjack::Data::EntityCheck:0x007fbba61120b0>, #<Flapjack::Data::EntityCheck:0x007fbba61105d0>, #<Flapjack::Data::EntityCheck:0x007fbba610aec8>\r\n```\r\nbut you're saying that no incidents are created in pagerduty for you? Is there any logging showing that the pagerduty-gateway has received a notification and it's trying to create the incidents in pagerduty? Eg something like:\r\n\r\n```\r\n2015-05-14T09:55:49.695253+09:30 [DEBUG] :: flapjack-pagerduty :: pagerduty notification event received: {\"media\"=>\"pagerduty\", \"address\"=>\"xxx\", \"id\"=>\"70221939250480-1431563149.693721\", \"rollup\"=>nil, \"contact_id\"=>\"8d5fd668-b4c4-481b-84be-9db4e5910110\", \"contact_first_name\"=>\"Ada\", \"contact_last_name\"=>\"Lovelace\", \"event_id\"=>\"foo-app-01:HTTP\", \"event_hash\"=>nil, \"state\"=>\"critical\", \"summary\"=>\"Simulated check output (test by operator)\", \"duration\"=>nil, \"last_state\"=>\"ok\", \"last_summary\"=>\"Simulated check output (test by operator)\", \"state_duration\"=>13521610, \"details\"=>nil, \"time\"=>1431563149, \"notification_type\"=>\"problem\", \"event_count\"=>1089, \"tags\"=>[\"foo-app-01\", \"http\"]}\r\n\r\n2015-05-14T09:55:49.695486+09:30 [DEBUG] :: flapjack-pagerduty :: processing pagerduty notification service_key: xxx, entity: foo-app-01, check: 'HTTP', state: critical, summary: Simulated check output (test by operator)\r\n```\r\n\r\n\r\n"}}