{"action":"closed","issue":{"url":"https://api.github.com/repos/cerner/cerner_tomcat/issues/24","repository_url":"https://api.github.com/repos/cerner/cerner_tomcat","labels_url":"https://api.github.com/repos/cerner/cerner_tomcat/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/cerner/cerner_tomcat/issues/24/comments","events_url":"https://api.github.com/repos/cerner/cerner_tomcat/issues/24/events","html_url":"https://github.com/cerner/cerner_tomcat/issues/24","id":183093094,"number":24,"title":"Verbose failure logs on cerner_tomcat provider failure","user":{"login":"cchesser","id":2358324,"avatar_url":"https://avatars.githubusercontent.com/u/2358324?v=3","gravatar_id":"","url":"https://api.github.com/users/cchesser","html_url":"https://github.com/cchesser","followers_url":"https://api.github.com/users/cchesser/followers","following_url":"https://api.github.com/users/cchesser/following{/other_user}","gists_url":"https://api.github.com/users/cchesser/gists{/gist_id}","starred_url":"https://api.github.com/users/cchesser/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/cchesser/subscriptions","organizations_url":"https://api.github.com/users/cchesser/orgs","repos_url":"https://api.github.com/users/cchesser/repos","events_url":"https://api.github.com/users/cchesser/events{/privacy}","received_events_url":"https://api.github.com/users/cchesser/received_events","type":"User","site_admin":false},"labels":[{"id":298108535,"url":"https://api.github.com/repos/cerner/cerner_tomcat/labels/enhancement","name":"enhancement","color":"0052cc","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2016-10-14T16:24:20Z","updated_at":"2016-12-27T20:21:36Z","closed_at":"2016-12-27T20:21:36Z","body":"We are getting large amount of contents in our chef-client logs, which are causing downstream failures in our chef-client runs. The typical downstream point of failure is the Chef reporter, which attempts to post all the resource updates (and failures), which eventually times out after minutes of trying to send the contents.\n\nHere is an [example log](https://gist.githubusercontent.com/cchesser/ec083cda125054073ec0dcb55a36a558/raw/455e150fe53eab66832d6b46129364a634f10db0/chef-client.log) (note, you need to view it through the raw view to see the full contents of the gist), when I changed the integration tests for this project to hit an invalid end-point for the health check.\n\nThis hash of attributes looks to be a result of our custom class definitions which extend our `Block` class  (ex. `class HealthCheckBlock < Block`), which have this massive expansion of definition.\n"}}
{"actor":{"display_login":"cchesser"}}