Public | Automated Build

Last pushed: 5 days ago
Short Description
Logstash container for ElasticSearch forwarding. Support provided for failover of Elasticsearch.
Full Description

Logstash Elastic High-Availability

Image to support Scale log capture with Logstash failover between Elasticsearch nodes.

This image is primarily intended to mitigate issues when Elasticsearch cluster nodes fail and are instantiated
elsewhere. Barring all nodes moving to other addresses, the watchdog process will discover the new locations from
Elasticsearch APIs and update the logstash pipeline to all available nodes.

If your Elasticsearch cluster is configured behind a load balancer(s), as it should be, you can disable the
watchdog functionality. This will still provide the template injection capability, but no introspection of
Elasticsearch cluster state APIs will be performed.

Configuration

This image provides a number of environment variables that can be used to tweak the behavior of logstash.

  • ELASTICSEARCH_URLS: One or more comma delimited full URLs to Elasticsearch nodes to bootstrap watchdog. For example,
    "http://node01:9200,http://node02:9200". The watchdog will continually update Logstash configuration as nodes are
    added or removed.
  • ELASTICSEARCH_LB: Boolean value indicating whether we are behind a load balancer (true) or not (false). If this
    value is set to false, watchdog functionality will be activated, otherwise it will be skipped.
  • LOGSTASH_ARGS: String of any arbitrary command-line arguments to pass to Logstash.
  • LOGSTASH_DEBUG: Case-sensitive boolean value indicating whether to output incoming messages to stdout. Must be true if output is desired, any other value will not output messages.
  • SLEEP_TIME: Time in seconds to sleep between watchdog checks of Elasticsearch nodes.
  • TEMPLATE_URI: URL to container accessible location of Logstash template config. See below for example.

Logstash Configuration Template

If there is a need to override the default configuration or specify additional filters, the following example contains
the minimum required configuration that should be used as a starting point for your config.

input {
  http {
    port => 80
    type => "app-healthcheck"
  }
}
filter {
  if [type] == "app-healthcheck" {
    drop { }
  }
}
output {
  elasticsearch {
    hosts => _ES_HOSTS_
  }
}

The http input handler and filter is needed to support Marathon health checks and drop all messages from that input.
If health checks are not needed all that is required is the output directive. The _ES_HOSTS_ value is required to
support the watchdog injection of nodes into the Logstash pipeline.

Docker Pull Command
Owner
geoint
Source Repository

Comments (0)