v18: Release 18

This release makes several changes which may require you to update your deployment manifest:

• upgraded elasticsearch to 1.4 (#91)
• no longer pre-install the HQ, marvel, or jetty elasticsearch plugins; instead you should now use the
  elasticsearch.plugins property documented in 4f3a3ff
• elasticsearch configuration is now YAML-based instead of JSON to make the cluster more easily customizable; you can
  now use the elasticsearch.config_options and elasticsearch.logging_options string properties to append
  deployment-specific settings to the generated defaults
• we dropped the logstash_forwarder and collectd jobs; use logsearch/shipper-boshrelease or your own solution if you
  want log and metric forwarding

Additionally, the following changes of less impact were made:

• a new rolling restart script in share/util to ease the cluster process
• the logstash_parser.outputs property can be used to send parsed events to a location in addition to logsearch's
  elasticsearch (#92 via @rkoster)
• a new, beta kibana job for testing the development version of kibana4 (4.0.0-beta3)
• the certificates and keys used in the examples/bosh-lite.yml manifest were rotated
• we've changed/improved our approach to project documentation, now maintaining content in the docs/ directory and
  published to http://www.logsearch.io

Upload this release to your BOSH using

bosh upload release https://s3.amazonaws.com/logsearch-boshrelease/releases/logsearch-18.tgz

v17: Release 17

This release most notably adds support for performance monitoring (via logsearch-shipper, and identifying deployment bottlenecks) and support for long-term, raw log archiving (via AWS S3).

• new feature: logsearch-shipper integration, including metric collectors for elasticsearch/redis and a Kibana dashboard
• new feature: enhanced event monitoring - optionally have ingestor and parser add timing metadata for helping to identify bottlenecks (#79)
• new feature: archiving - optionally archive/compress all messages into AWS S3; includes basic scripts for restoring those archived files (#78)
• enhancement: simplify the drain script used for blocking elasticsearch deploys to avoid downtime (#78)
• change: the host and sslsubject fields in the ssl-syslog ingestor are now named @ingestor.remote_host and @ingestor.sslsubject (#69)
• bug: fix logstash config issue when logstash_parser.filters is empty (#84)

Upload this release to your BOSH using:

bosh upload release https://s3.amazonaws.com/logsearch-boshrelease/releases/logsearch-17.tgz

v16: Release 16

This adds TLS support to the syslog ingestor and significantly changes how logstash filters are configured.

Backward Compatibility Break - the logstash.filters is no longer an array of files to extract and dynamically compose a set of filters. The value must now be the final concatenated form of the filters you want to use (excluding the wrapping filter { ... } parts). Typically you'll automatically update this from a build artifact.

• BREAKING CHANGE: the logstash.filters property now expects a string of the literal filter rules logstash should use (#58)
• ADD: syslog_tls ingestor support (#59)
• ADD: drain script for elasticsearch - currently disabled, by default, with the elasticsearch.drain property (#51)

v15: Release 15

This upgrades most dependencies in the stack and makes several improvements for
deployments running at larger scales.

• UPGRADE: elasticsearch to 1.2.1 (#37)
• UPGRADE: logstash to 1.4.1 (#45)
• UPGRADE: kibana to 3.1.0 (#44)
• UPGRADE: marvel to 1.2.1 (#37)
• UPGRADE: logsearch-filters-common to v16
• FIX: relp ingestor when debug is enabled (#53)
• FIX: elasticsearch rolling its own requests.log file (#47)
• ADD: disk/df metrics to collectd's default plugins (#64)
• ADD: configurable elasticsearch.log_level setting, defaulting to INFO (#52)
• REMOVE: elasticsearch garbage collection logging (#55)

v14: Release 14

This release touches all the packages and jobs to ensure blobs will be re-loaded and avoid the checksum mismatch errors caused by Release 13.

Release 13

Note: upgrading to this release is broken, you should skip to v14.

With this release we've switched away from authenticated, encrypted blobs on S3.
For users of prior releases, there is a one-time step required for this process.

For development, you may need to clear the blob symlinks you have locally to
avoid checksum mismatch errors. You can use the following command:

git clean -d -f -x .final_builds/

Blobs from prior releases are still available in the S3 blobstore. If you need
to switch to a prior release, you'll need to run through the same cleaning
process.