You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some lines in my rsyslog log files on Debian (the ones coming from the imtcp module) were not matched properly because of slight differences in the format of some fields :
the log_pid field sometimes contains a point
the : after the PID is sometimes missing
Here is an example : 2025-04-21T12:24:51.761734+02:00 myhostname kernel [499130.569180] [UFW BLOCK] IN=enX0...
I'm not sure if these differences are due to a misconfiguration on my part. I'm using the latest version of rsyslog with this configuration : $ActionFileDefaultTemplate RSYSLOG_FileFormat.
This pull requests offers to fix this on the regex's side in case other users have the same issue.
Here is the line that I will add to the sample section of the json file, with a missing colon : 2025-04-15T17:36:24.135033+02:00 myhostname sshd[730594] Disconnected from authenticating user root 218.92.0.111 port 37632 [preauth]
Regarding the dot in the log_pid field, actually, I was mistaken by the missing colon. In my original example (kernel [499130.569180] [UFW BLOCK]) the colon is supposed to be after kernel and the numbers in brackets are part of the body, not log_pid. After looking further, I cannot find an example with a dot in the log_pid field. Would you prefer that I revert the [\\d\\.] in this pull request?
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
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.
Some lines in my
rsysloglog files on Debian (the ones coming from theimtcpmodule) were not matched properly because of slight differences in the format of some fields :log_pidfield sometimes contains a point:after the PID is sometimes missingHere is an example :
2025-04-21T12:24:51.761734+02:00 myhostname kernel [499130.569180] [UFW BLOCK] IN=enX0...I'm not sure if these differences are due to a misconfiguration on my part. I'm using the latest version of
rsyslogwith this configuration :$ActionFileDefaultTemplate RSYSLOG_FileFormat.This pull requests offers to fix this on the regex's side in case other users have the same issue.