I have a script that sends effectively yum outputs to receivers/simple. props.conf says
[yumstuff] DATETIME_CONFIG = LINE_BREAKER = ([\r\n]+) NO_BINARY_CHECK = true category = Miscellaneous ...
See more...
I have a script that sends effectively yum outputs to receivers/simple. props.conf says
[yumstuff] DATETIME_CONFIG = LINE_BREAKER = ([\r\n]+) NO_BINARY_CHECK = true category = Miscellaneous pulldown_type = 1
I expect the each post to be one event. But some posts get broken into multiple events for unknown reasons. My guess is that those posts are longer, although I couldn't find any applicable limit in limits.conf. The broken ones are not all that long to start. I examined one that was broken into three "events ". Combined, they have 18543 chars, 271 lines. The closest attribute in limits.conf I can find is maxchars, but that's for [kv] only, and the limit is already high:
[kv] indexed_kv_limit = 1000 maxchars = 40960
The way it is broken also confuses me. My post begins with a timestamp, followed by some bookkeeping kv pairs, then yum output. If this breakage is caused by limits, I would expect the event containing the first part to be the biggest, to the extent it exceeds that limit. But in general, the "event" corresponding to the end of the post is the biggest; even stranger, the middle "event" generally is extremely small containing only one line. In the post I examined, for example, the first "event" contained 6710 chars, the second, 71 chars, the last, 11762 chars. The breaking points are not special, either. For example,
2022-02-09T19:51:28+00:00 ...
...
---> Package iwl6000g2b-firmware.noarch 0:18.168.6.1-79.el7 will be updated
---> Package iwl6000g2b-firmware.noarch 0:18.168.6.1-80.el7_9 will be an update
<break>
---> Package iwl6050-firmware.noarch 0:41.28.5.1-79.el7 will be updated
<break>
---> Package iwl6050-firmware.noarch 0:41.28.5.1-80.el7_9 will be an update
---> Package iwl7260-firmware.noarch 0:25.30.13.0-79.el7 will be updated
...
Where should I look?