{"push_id":1007260893,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"08101fd4654ffbf7ca6331427a5d895b1db0f008","before":"8976263153f7fe7d294df74a49b3f5d9fbcd68ed","commits":[{"sha":"491aff0b88bc3dac13ea9180c952854fd0a67684","author":{"email":"620b806f320cd81167b92b56b5ed29958b3c94d2@mirantis.com","name":"Éric Lemoine"},"message":"Make Heka send logs to Elasticsearch\n\nThis patch includes changes relative to integrating Heka with\nElasticsearch and Kibana.\n\nThe main change is the addition of an Heka ElasticSearchOutput plugin\nto make Heka send the logs it collects to Elasticsearch.\n\nSince Logstash is not used the enable_elk deploy variable is renamed\nto enable_central_logging.\n\nIf enable_central_logging is false then Elasticsearch and Kibana are\nnot started, and Heka won't attempt to send logs to Elasticsearch.\n\nBy default enable_central_logging is set to false. If\nenable_central_logging is set to true after deployment then the Heka\ncontainer needs to be recreated (for Heka to get the new\nconfiguration).\n\nThe Kibana configuration used property names that are deprecated in\nKibana 4.2. This is changed to use non-deprecated property names.\n\nPreviously logs read from files and from Syslog had a different Type\nin Heka. This is changed to always use \"log\" for the Type. In this\nway just one index instead of two is used in Elasticsearch, making\nthings easier to the user on the visualization side.\n\nThe HAProxy configuration is changed to add entries for Kibana.\nKibana server is now accessible via the internal VIP, and also via\nthe external VIP if there's one configured.\n\nThe HAProxy configuration is changed to add an entry for\nElasticsearch. So Elasticsearch is now accessible via the internal\nVIP. Heka uses that channel for communicating with Elasticsearch.\n\nNote that currently the Heka logs include \"Plugin\nelasticsearch_output\" errors when Heka starts. This occurs when Heka\nstarts processing logs while Elasticsearch is not yet started. These\nare transient errors that go away when Elasticsearch is ready. And\nwith buffering enabled on the ElasticSearchOuput plugin logs will be\nbuffered and then retransmitted when Elasticsearch is ready.\n\nChange-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb\nImplements: blueprint central-logging-service","distinct":true,"url":"https://api.github.com/repos/openstack/kolla/commits/491aff0b88bc3dac13ea9180c952854fd0a67684"},{"sha":"08101fd4654ffbf7ca6331427a5d895b1db0f008","author":{"email":"d95b56ce41a2e1ac4cecdd398defd7414407cc08@review.openstack.org","name":"Jenkins"},"message":"Merge \"Make Heka send logs to Elasticsearch\"","distinct":true,"url":"https://api.github.com/repos/openstack/kolla/commits/08101fd4654ffbf7ca6331427a5d895b1db0f008"}]}