Configuring mulitple remote servers#53
Merged
saz merged 2 commits intosaz:masterfrom Feb 10, 2014
Merged
Conversation
Owner
|
Please rebase your changes to the current master and I'll be happy to merge them. Thanks! |
added 2 commits
February 7, 2014 10:40
…ts the default logging format for remote and local logging.
Contributor
Author
|
This is now rebased on PR #52 so merge this afterwards. Note that using |
saz
added a commit
that referenced
this pull request
Feb 10, 2014
Configuring mulitple remote servers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This configures multiple remote servers provided as a list of key/value pairs. Supplying such a list over-rides the usual method of providing a single remote server.
This new method also allows each server to specify the log matching pattern, the protocol, host, port, and log format.
It should be backwards compatible with the previous single remote method and not trigger a new major version.