[Arista NG Firewall] Correct Grok pattern due to change in Syslog message format. #12176
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.




Type of change
Proposed commit message
A recent update to Arista NG Firewall changed the Syslog message format slightly. Where there used to be two spaces preceding the message body, the new format only includes a single space. The updated Grok pattern accounts for both the old, double-spaced format and the new single-spaced format.
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Modified the
defaultingest pipeline with the proposed Grok pattern change, and the messages are now parsing again properly.Related issues