cisco-parser: allow leading dot in timestamps - #3843
Merged
bazsi merged 2 commits intoNov 20, 2021
Conversation
added 2 commits
November 19, 2021 18:00
We've received an example log from the community, in which the timestamp had a leading dot. I've slightly modified the hostname and the message parts ``` <180>782431: machine1: .Nov 18 21:03:22.631 GMT: %CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on TenGigabitEthernet. ``` I haven't found an official documentation about the leading dot yet, only cisco community posts, e.g.: https://community.cisco.com/t5/other-network-architecture/logging-shows-an-asterisk-quot-jan-13-11-05-40-quot/td-p/564707 https://community.cisco.com/t5/other-security-subjects/log-entries-with-a-dot-before-timestamp/td-p/590136 The leading asterisk is better documented in multiple system guides: https://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-1/system_monitoring/command/reference/sysmon_cr41crs_chapter4.html#wp255058350 > If the system clock has not been set, the date and time are preceded by an asterisk (*), which indicates that the date and time have not been set and should be verified. Or here: https://www.cisco.com/c/en/us/td/docs/routers/access/wireless/software/guide/SysMsgLogging.html#wp1054710 Signed-off-by: Gabor Nagy <gabor.nagy@oneidentity.com>
Signed-off-by: Gabor Nagy <gabor.nagy@oneidentity.com>
Contributor
|
Build SUCCESS |
MrAnno
approved these changes
Nov 19, 2021
MrAnno
left a comment
MrAnno
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the thorough explanation :)
bazsi
approved these changes
Nov 20, 2021
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
4 participants
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.
We've received an example log from the community, in which the timestamp had a leading dot.
I've slightly modified the hostname and the message parts
<180>782431: machine1: .Nov 18 21:03:22.631 GMT: %CDP-4-NATIVE_VLAN_MISMATCH: Native VLAN mismatch discovered on TenGigabitEthernet.I haven't found an official documentation about the leading dot yet, only cisco community posts, e.g.:
https://community.cisco.com/t5/other-network-architecture/logging-shows-an-asterisk-quot-jan-13-11-05-40-quot/td-p/564707
https://community.cisco.com/t5/other-security-subjects/log-entries-with-a-dot-before-timestamp/td-p/590136
The leading asterisk is better documented in multiple system guides:
https://www.cisco.com/c/en/us/td/docs/routers/crs/software/crs_r4-1/system_monitoring/command/reference/sysmon_cr41crs_chapter4.html#wp255058350
Or here: https://www.cisco.com/c/en/us/td/docs/routers/access/wireless/software/guide/SysMsgLogging.html#wp1054710