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
Because milliseconds is a common resolution for time spans in this behavior.
Latency with 1 or 2 seconds is quite special and not that much useful - at least a integer number.
Hy
Describe the bug
With Elasticsearch output the term dnstap.latency is stored as integer - i guess in seconds
To Reproduce
Export dnstap to elasticsearch v8.17
Expected behavior
The Latecy should be stored in Milliseconds.
Additional context
Best regards
A
The text was updated successfully, but these errors were encountered: