Logstash 2.0.0

Release Notes

General

  • Added beats input in the default plugins list
  • Update to JRuby 1.7.22
  • Better shutdown handling in Logstash core and its plugins. Previously, the shutdown handling was through an injected exception which made it non-deterministic. The change introduces cleaner APIs in the core to signal a shutdown event which can be used by the plugins (#3210)
  • Upgrade to JrJackson version 0.3.5 which fixes numerous bugs and also provides performance boost for JSON handling (#3702)
  • Better defaults: Out of the box, the default value of the filter_workers (-w) setting will be set to half of the CPU cores of the machine. Increasing the workers provides parallelism in filter execution which is crucial when doing heavier processing like complex grok patterns or the useragent filter. You can still override the default by passing -w flag when starting Logstash (#3870)
  • Improved default security configuration for SSL/TLS. Default is now TLS1.2 (#3955)
  • Added obsolete setting which will cause a configuration error if a config marked obsolete is used. The purpose of :obsolete is to help inform users when a setting has been completely removed. The lifecycle of a plugin setting is now 4 phases: available, deprecated, obsolete, deleted. (#3977)

Input

  • Obsolete config settings (which were already deprecated): debugformatcharsetmessage_format. Logstash will not start if you use these settings.

Output

  • Obsolete config settings (which were already deprecated): typetagsexclude_tags. Logstash will not start if you use these settings.
  • Elasticsearch (#237):
    • Changed the default from node to http protocol.
    • Backward incompatible config options. Renamed host to hosts
    • Separate plugins for Java clients: transport and node options are not packaged by default but can be installed using the logstash-output-elasticsearch_java plugin.
    • Java client defaults to transport protocol
  • Kafka:
    • Update to new 0.8.2 Java producer API with new producer configuration
    • Backward incompatible config settings introduced to match Kafka options
  • HTTP: Fixed memory leak in http output with usage of manticore library (#24)

Filter

  • Obsolete config settings (which were already deprecated): typetagsexclude_tags. Logstash will not start if you use these settings.
  • Fixed metrics filter to work with ES 2.0 changes which does not allow dots in field names
  • Performance improvements in GeoIP and User Agent (#12)