Point to Elastic instead of logstash.net

closes #610

README.md

@@ -13,7 +13,7 @@ Provides [logback](http://logback.qos.ch/) encoders, layouts, and appenders to l
 
 Supports both regular _LoggingEvents_ (logged through a `Logger`) and _AccessEvents_ (logged via [logback-access](http://logback.qos.ch/access.html)).
 
-Originally written to support output in [logstash](http://logstash.net/)'s JSON format, but has evolved into a highly-configurable, general-purpose, structured logging mechanism for JSON and other Jackson dataformats.
+Originally written to support output in [logstash](https://www.elastic.co/guide/en/logstash/current)'s JSON format, but has evolved into a highly-configurable, general-purpose, structured logging mechanism for JSON and other Jackson dataformats.
 The structure of the output, and the data it contains, is fully configurable.
 
 #### Contents:
@@ -245,7 +245,7 @@ in your `logback-access.xml`, like this:
 ```
 
 
-To receive syslog/UDP input in logstash, configure a [`syslog`](http://www.logstash.net/docs/latest/inputs/syslog) or [`udp`](http://www.logstash.net/docs/latest/inputs/udp) input with the [`json`](http://www.logstash.net/docs/latest/codecs/json) codec in logstash's configuration like this:
+To receive syslog/UDP input in logstash, configure a [`syslog`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-syslog.html) or [`udp`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-udp.html) input with the [`json`](https://www.elastic.co/guide/en/logstash/current/plugins-codecs-json.html) codec in logstash's configuration like this:
 ```
 input {
   syslog {
@@ -314,8 +314,7 @@ If the RingBuffer is full (e.g. due to slow network, etc), then events will be d
 The TCP appenders will automatically reconnect if the connection breaks.
 However, events may be lost before Java's socket realizes the connection has broken.
 
-To receive TCP input in logstash, configure a [`tcp`](http://www.logstash.net/docs/latest/inputs/tcp)
-input with the [`json_lines`](http://www.logstash.net/docs/latest/codecs/json_lines) codec in logstash's configuration like this:
+To receive TCP input in logstash, configure a [`tcp`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-tcp.html) input with the [`json_lines`](https://www.elastic.co/guide/en/logstash/current/plugins-codecs-json_lines.html) codec in logstash's configuration like this:
 
 ```
 input {
@@ -353,6 +352,8 @@ The keep alive message defaults to unix line ending (`\n`), but can be changed b
 
 Any other value will be used as-is.
 
+The keep alive message is encoded in `UTF-8` by default. This can be changed by setting the `keepAliveCharset` property to the name of the desired charset.
+
 
 #### Multiple Destinations
 
@@ -630,8 +631,7 @@ All the customizations that [logback](http://logback.qos.ch/manual/usingSSL.html
 (such as configuring cipher specs, protocols, algorithms, providers, etc.)
 are supported by the `Logback*TcpSocketAppender`s.
 
-See the logstash documentation for the [`tcp`](http://www.logstash.net/docs/latest/inputs/tcp) input
-for how to configure it to use SSL.
+See the logstash documentation for the [`tcp`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-tcp.html) input for how to configure it to use SSL.
 
 
 ### Async Appenders
@@ -886,7 +886,7 @@ The `LogstashLayout` and `LogstashAccessLayout` can be configured the same way a
 the `LogstashEncoder` and `LogstashAccessEncoder`.  All the other examples
 in this document use encoders, but the same options apply to the layouts as well.
 
-To receive file input in logstash, configure a [`file`](http://www.logstash.net/docs/latest/inputs/file) input in logstash's configuration like this:
+To receive file input in logstash, configure a [`file`](https://www.elastic.co/guide/en/logstash/current/plugins-inputs-file.html) input in logstash's configuration like this:
 
 ```
 input {