The current collectd example that can be used together with the exec plugin prints bogus information about flows.
This issue is caused by the memset in c-collectd.c:512. The desired behavior should be that the executable does not only print statistics between collectd time intervals and resets them afterwards no matter if the flow is still active (e.g. did neither end nor timed out).
Instead, it should also process idle and end events to validate if a flow is still active and modify the statistics printed to stdout in a proper way.
utoni
commented
9 months ago
The current collectd example that can be used together with the
execplugin prints bogus information about flows. This issue is caused by the memset inc-collectd.c:512. The desired behavior should be that the executable does not only print statistics between collectd time intervals and resets them afterwards no matter if the flow is still active (e.g. did neither end nor timed out).Instead, it should also process
idleandendevents to validate if a flow is still active and modify the statistics printed to stdout in a proper way.