-
Notifications
You must be signed in to change notification settings - Fork 464
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RCPTID skipping numbers when suppression is enabled #4608
Comments
|
Yes, but suppression messages go through a different path otherwise they would have the RCPTID, Instead they have their own counter. |
What exactly would you like to achieve? Based on the discussion in #4363, you are seeking a way to uniquely identify each message in syslog-ng.
The suppression message is no exception: it is new message created by syslog-ng dynamically, so it increments the
These IDs were assigned to the suppression summary messages, but you can't see them because the Unfortunately, rewriting the |
This PR should add the capability to send a monotonic sequence ID: Let me know if that helps. |
syslog-ng
Version of syslog-ng
Platform
Debug bundle
Not available
Issue
Failure
In the following log excerpt:
It is missing IDs 1332919, 1332942, 1332985.
It is like after the suppression message RCPTID jumped one number.
We are using
rewrite r_sequence_id {set("${RCPTID}" value(".SDATA.meta.sequenceId"));};
to set the sequence IDSteps to reproduce
Force syslog-ng to suppress some messages
Configuration
Input and output logs (if possible)
The text was updated successfully, but these errors were encountered: