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
Firstly, thank you for the library.
In the goflow/utils/sflow.go file, there are the following blocks of code:
Defining "ts":
ts := uint64(time.Now().UTC().Unix())
if pkt.SetTime {
ts = uint64(pkt.RecvTime.UTC().Unix())
}
Setting TimeReceived, TimeFlowStart, and TimeFlowEnd:
for _, fmsg := range flowMessageSet {
fmsg.TimeReceived = ts
fmsg.TimeFlowStart = ts
fmsg.TimeFlowEnd = ts
}
Currently, there is no difference between TimeFlowStart / TimeFlowEnd and TimeReceived. However, when the flag "SetTime" is set to "true", it would be very useful to distinguish between these timestamps.
Thank you!
The text was updated successfully, but these errors were encountered:
tgragnato
pushed a commit
to tgragnato/goflow
that referenced
this issue
Aug 14, 2024
This pull request adds the optional -transport.kafka.scram flag,
which tells the Kafka transport to use SASL/SCRAM for authentication.
This allows goflow2 to work with AWS Managed Service for Kafka (MSK)
which does not support SASL/PLAIN.
Co-authored-by: Brian Landers <[email protected]>
Co-authored-by: lspgn <[email protected]>
Firstly, thank you for the library.
In the goflow/utils/sflow.go file, there are the following blocks of code:
Currently, there is no difference between TimeFlowStart / TimeFlowEnd and TimeReceived. However, when the flag "SetTime" is set to "true", it would be very useful to distinguish between these timestamps.
Thank you!
The text was updated successfully, but these errors were encountered: