Use 4560 (log4j default) as default port
Fix link to FPM
HOSTPORT didn't parse anything useful

Changed HOSTPORT to a simple combination of IPORHOST and POSINT. What was the old pattern supposed to do and what does =~ mean?
Refactor netflow codec.

Netflow field definitions are now extracted to a bundled YAML file and also
introduces a new config directive to specify an additional YAML file that
can be used to augment the built-in list. This means adding new Netflow field
types doesn't require a rebuild of Logstash.

TODO Work out how to get the YAML file added to the jar.
Add example YAML to documentation
Pull Netflow YAML file into the jar.
Added file with patterns for JUNOS 11.4 RT_FLOW log messages
[rabbitmq] Change auto-delete and exclusive defaults to `false`

Otherwise the queue will be removed when Logstash is shutdown or
restarted. In general, both attributes don't make much sense
in the context of Logstash. Also, most if not all popular
RabbitMQ clients default both attributes to `false`.

This is a breaking change so perhaps requires a more
visible change log entry.

Fixes #859.
initial version of getting-start asciidoc (WIP)
formatting "improvements"
Update changelog from 1.3.1-head
Upgrade ES to 0.90.8
repo doc nits... the copy editor in me
add 'package' to repo link
Add some perf tests
Add fast iso8601-string to Ruby Time converter; based on research here: https://github.com/jordansissel/experiments/tree/master/ruby/time-iso8601-parsing
Use much faster "@timestamp" iso8601 string parsing

Also use constants for most strings to avoid creating new string objects
pointlessly.

Running the perf test:
% SPEEDTEST=1 bin/logstash rspec spec/event.rb -e speed

* before patch: event @timestamp parse rate: 19118/sec
* after patch: event @timestamp parse rate: 320718/sec

This was done in response to
https://github.com/octplane/logstash_benchmark in which another user
found something to be slow in logstash and decided to write something
from scratch to replace logstash.

Bugs are not features.
Slowness is a bug. We can improve it, see? :)
Use faster time parsing strategy.

Joda-Time to milliseconds, Time.at(milliseconds / 1000.0).utc

perf tests:

% SPEEDTEST=1 bin/logstash rspec spec/filters/date_performance.rb -e speed
- before patch: date parse rate: 43687.1996505024
- after patch: date parse rate: 57836.899942163094

Research here:
https://github.com/jordansissel/experiments/tree/master/ruby/time-iso8601-parsing
Merge pull request #894 from jordansissel/date-and-json-perf-testing

Improve @timestamp and Date filter parsing speeds
Merge pull request #887 from jordansissel/prep-for-1.3.2

Prep for 1.3.2