Adding a new line to the end of the message to ensure that the logstash server interprets as a complete log message.
Merge pull request #2 from gwhitelaw/add_new_line_to_flush_socket

Logs sent to logstash are interpreted as stream and therefore are incorrectly parsed
Merged bugfix and update npm version to 0.1.2
Added ability to configure connection retry count

Also added an option to never stop trying for daemon processes.
Merge pull request #3 from cjsaylor/daemon-connection-retry

Added ability to configure connection retry count
Minor versio up after merging new feature
Added SSL support

Includes:
* SSL verification if the logstash is configured to verify the sender.
This is tested by passing the public key of the client as a CA to the
SSL TPC server.
Added configuration for SSL (among other things).
Cleaned up configuration markdown.
Merge pull request #4 from cjsaylor/ssl-support

SSL Support
Pump version & update contributors
Winston versio upgrade 0.6.2 -> 0.7.2
Allows to define 0 reconnections

I changed the constructor condition to accept 0 max_connect_retries and
I also changed the counter to manage 0 accordingly and use any negative
number as infinite retries
Reset retries connect and emit error when silent mode

I added the 'connect' event listener to socket to reset the connection
retries counter and 'error' emit to the transport when the maximum
connect retries is reached and the transport is 'silent' mode
Added test for 'error' emit when it swaps to silent

I added a test to check that transport emit an 'error' message when it
reaches the maximum connection retries and it swaps to ```silent``` mode
ca option and reporting errors no ECONNREFUSED

I added the ```ca``` options to provide an array with the CAs that
winston-logstash secure socket accept, so it is provided to node client
secure socket connection.

I also added a checking in socket ```error``` listener to report to
transport eventEmitter when socket received an error different from
ECONNREFUSED
Added test for ca option and error reporting

I added a test to check the ca option and the error reporting so, I
regenerated the certificates and keys and provided another to check
which provoke an error on the transport socket to check the implemented
error reporting.

I also added a shell script to regenerate the server key and certificate
Merge pull request #6 from ifraixedes/if-tls-client-subjectalname

Provided CA parameter to pass to the tls socket connection and socket error non ECONNREFUSED reporting
Merge branch 'if-allow-0-max-conn-retries' of github.com:ifraixedes/winston-logstash into ifraixedes-if-allow-0-max-conn-retries

Conflicts:
	lib/winston-logstash.js
Merge pull request #8 from ifraixedes/if-emit-error-max-conn-reties-reached

If emit error when max connections reties has been reached