Allow optional space between sysloghost and colon. #2
Conversation
This file contains 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
Closes elastic/logstash#2101. If a Cisco ASA has a logging device-id set, the syslog message emitted contains an additional space after the device-id and therefore does not match the grok pattern CISCO_TAGGED_SYSLOG. An optional space should be allowed by the pattern between the device-id (which is captured as sysloghost) and the colon character.
|
The work email address with which I signed the CLA is a secondary address on my github account. Please update your CLA check to accommodate multiple email addresses. See past discussion on the original PR, elastic/logstash#2102 |
This was referenced Jun 3, 2015
|
I can confirm this fixes it for me. |
|
This has been merged in 0f077c1 |
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.
Closes elastic/logstash#2101. If a Cisco ASA has a logging
device-id set, the syslog message emitted contains an additional space
after the device-id and therefore does not match the grok pattern
CISCO_TAGGED_SYSLOG. An optional space should be allowed by the pattern
between the device-id (which is captured as sysloghost) and the colon
character.