Actions
Feature #1300
openprofiling: per flow recording of profiling data
Description
Flows track number of packets, so adding a total ticks count would allow calculating an average.
We could then output (in the flow log):
- absolute and relative cost of a flow
Also, a simple keyword could perhaps match on this. Then we'd alert on overly expensive flows (and even drop/pass them?).
Both should greatly help debugging performance issues.
Updated by Andreas Herz almost 9 years ago
- Assignee set to OISF Dev
- Target version set to TBD
Updated by Victor Julien about 6 years ago
- Effort set to low
- Difficulty set to medium
I think this would be quite easy now. Just capture the ticks within the lock of the FlowWorker and store that in the Flow in a new field.
Actions