-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
mqtt: enable limiting of logged message length #11053
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #11053 +/- ##
==========================================
+ Coverage 80.63% 83.65% +3.01%
==========================================
Files 922 922
Lines 250137 250338 +201
==========================================
+ Hits 201699 209417 +7718
+ Misses 48438 40921 -7517
Flags with carried forward coverage won't be shown. Click here to find out more. |
ddb59da
to
b5d0b3a
Compare
b5d0b3a
to
5edd982
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a documentation update to doc/userguide/configuration/suricata-yaml.rst
Hmm, it looks like the included file Also, I don't think that the logging options should go into |
New PR: #11054 11054 |
I think |
I see that Sascha has addressed this, but just to answer - it seems to be what we're following, indeed. |
https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html
https://suricata.io/about/contribution-agreement/ (note: this is only required once)
Link to redmine ticket: https://redmine.openinfosecfoundation.org/issues/6984
Describe changes:
msg-log-limit
option to enable optional truncation of the message payloads in MQTT.