{"action":"opened","issue":{"url":"https://api.github.com/repos/18F/cg-dashboard/issues/515","repository_url":"https://api.github.com/repos/18F/cg-dashboard","labels_url":"https://api.github.com/repos/18F/cg-dashboard/issues/515/labels{/name}","comments_url":"https://api.github.com/repos/18F/cg-dashboard/issues/515/comments","events_url":"https://api.github.com/repos/18F/cg-dashboard/issues/515/events","html_url":"https://github.com/18F/cg-dashboard/issues/515","id":168207925,"number":515,"title":"Activity log for cloud foundry events per application","user":{"login":"jeremiak","id":780941,"avatar_url":"https://avatars.githubusercontent.com/u/780941?v=3","gravatar_id":"","url":"https://api.github.com/users/jeremiak","html_url":"https://github.com/jeremiak","followers_url":"https://api.github.com/users/jeremiak/followers","following_url":"https://api.github.com/users/jeremiak/following{/other_user}","gists_url":"https://api.github.com/users/jeremiak/gists{/gist_id}","starred_url":"https://api.github.com/users/jeremiak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeremiak/subscriptions","organizations_url":"https://api.github.com/users/jeremiak/orgs","repos_url":"https://api.github.com/users/jeremiak/repos","events_url":"https://api.github.com/users/jeremiak/events{/privacy}","received_events_url":"https://api.github.com/users/jeremiak/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-28T22:05:09Z","updated_at":"2016-07-28T22:05:09Z","closed_at":null,"body":"In order for developers to troubleshoot their applications, they need to understand what recent system events occurred.\r\n\r\nAcceptance criteria:\r\n- [ ] An activity list of [platform events](https://apidocs.cloudfoundry.org/226/events/list_all_events.html) with timestamps\r\n- [ ] Timestamps should be in the format of \"Mar 09 2017   05:17:24\"\r\n- [ ] Crash events should be prominent\r\n- [ ] Any changes due to user activity (quota changes, services bound, ssh logins, etc) should be prominent but different from crash events"}}
{"actor":{"display_login":"jeremiak"}}