You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using this library to parse OVS flows, and I need the n_bytes and n_packets information of the flow. I noticed that these fields are ignored in the UnmarshalText function. I think it would be beneficial if I could access n_bytes and n_packets directly from the Flow structure.
I solved my problem by using the DumpAggregate function. However, in my case, I need to retrieve the n_bytes of many flows, which results in numerous DumpAggregate calls instead of a single DumpFlows call.
I'm curious whether this behavior is intentional or simply not yet implemented. If there are no other considerations, I would be willing to contribute some code to address this issue.
The text was updated successfully, but these errors were encountered:
I am using this library to parse OVS flows, and I need the
n_bytes
andn_packets
information of the flow. I noticed that these fields are ignored in theUnmarshalText
function. I think it would be beneficial if I could accessn_bytes
andn_packets
directly from theFlow
structure.I solved my problem by using the
DumpAggregate
function. However, in my case, I need to retrieve then_bytes
of many flows, which results in numerousDumpAggregate
calls instead of a singleDumpFlows
call.I'm curious whether this behavior is intentional or simply not yet implemented. If there are no other considerations, I would be willing to contribute some code to address this issue.
The text was updated successfully, but these errors were encountered: