aboutsummaryrefslogtreecommitdiff
path: root/ansible/roles/common/templates/heka-haproxy.toml.j2
AgeCommit message (Collapse)AuthorFilesLines
2016-11-15Remove Ansible from KollaSteven Dake1-9/+0
Change-Id: I5396e4b9927d3e65b6aa4185238a43a4765a996b
2016-04-03Make Heka write Keepalived logs to dedicated directoryCarlos Cesario1-8/+1
Currently Heka writes the keepalived logs in /var/log/kolla/haproxy/keepalived.log. This commit changes this to /var/log/kolla/keepalived/keepalived.log. Closes-Bug: #1565499 Change-Id: I3033097bd77ddbf72948697b34a6a499ea903083
2016-03-09Merge "Copy the logs out of the container"Jenkins1-0/+2
2016-03-09Copy the logs out of the containerJeffrey Zhang1-0/+2
Heka logs almost done. When testing, The collected logs can copy to the /tmp/logs folder, which will be handle by the gate. This will be very useful for our gate debug. TrivialFix Change-Id: I06ca8ebd13933bfd15cb2fb5e53fc3038b17b8c3
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine1-2/+2
This patch includes changes relative to integrating Heka with Elasticsearch and Kibana. The main change is the addition of an Heka ElasticSearchOutput plugin to make Heka send the logs it collects to Elasticsearch. Since Logstash is not used the enable_elk deploy variable is renamed to enable_central_logging. If enable_central_logging is false then Elasticsearch and Kibana are not started, and Heka won't attempt to send logs to Elasticsearch. By default enable_central_logging is set to false. If enable_central_logging is set to true after deployment then the Heka container needs to be recreated (for Heka to get the new configuration). The Kibana configuration used property names that are deprecated in Kibana 4.2. This is changed to use non-deprecated property names. Previously logs read from files and from Syslog had a different Type in Heka. This is changed to always use "log" for the Type. In this way just one index instead of two is used in Elasticsearch, making things easier to the user on the visualization side. The HAProxy configuration is changed to add entries for Kibana. Kibana server is now accessible via the internal VIP, and also via the external VIP if there's one configured. The HAProxy configuration is changed to add an entry for Elasticsearch. So Elasticsearch is now accessible via the internal VIP. Heka uses that channel for communicating with Elasticsearch. Note that currently the Heka logs include "Plugin elasticsearch_output" errors when Heka starts. This occurs when Heka starts processing logs while Elasticsearch is not yet started. These are transient errors that go away when Elasticsearch is ready. And with buffering enabled on the ElasticSearchOuput plugin logs will be buffered and then retransmitted when Elasticsearch is ready. Change-Id: I6ff7a4f0ad04c4c666e174693a35ff49914280bb Implements: blueprint central-logging-service
2016-02-19Make Heka collect HAProxy and Keepalived logsÉric Lemoine1-0/+14
Partially implements: blueprint heka Change-Id: I7e2bf4e520fa14fd40e3b329f3b2998ae6ea47f4