aboutsummaryrefslogtreecommitdiff
path: root/docker/heka/plugins/decoders/os_swift_log.lua
AgeCommit message (Collapse)AuthorFilesLines
2017-02-24Remove heka imageJeffrey Zhang1-49/+0
Heka is removed and replaced by fluentd. Change-Id: I4ed0f61b02bea5dcb02b61a9eb99e3ff3f460682
2016-08-06Fix inconsistencies in git urlRobin Naundorf1-1/+1
Github is just a mirror of the OpenStack git-repo. Changed from Github to OpenStack git url wherever possible. Change-Id: I7941ef86967de4efe7f23ff9fb11ec86c793901e
2016-03-05Make Heka send logs to ElasticsearchÉric Lemoine1-1/+1
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-22Fix Swift loggingÉric Lemoine1-0/+49
Swift uses Syslog, but it uses a custom log format. So this commit adds a specific Heka decoder for Swift. It also increases the log level from "warning" to "info" to make Swift more verbose. Note that "info" is the default log level in Swift. And it disables the Heka configuration for Swift when "enable_swift" is set to "no". This prevents Heka from creating 15 empty Swift log files in the logs volume. Partially implements: blueprint heka Change-Id: If7a7d0707e71be2957178e2d45b5de51b788232e