-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement draft-ietf-opsawg-ipfix-on-path-telemetry #21
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! 👍
@@ -51,5 +51,10 @@ func main() { | |||
ingressIfName = c.Ipfix.IngressInterface | |||
} | |||
|
|||
client.New(ingressIfName, raddr) | |||
interval := c.Ipfix.Interval |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be nice if the readme could understand how to use this option.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wrote how to configure interval in getting-started.md
Description
Type of change
Motivation and Context
To obtain and export on-path delay metrics
How is This Tested?
Tested with packets with IOAM timestamps inserted by VPP (https://github.com/network-analytics/vpp/tree/feature/ipfix-onpath-telemetry)
Other Information
Change the licence of xdp code to
Dual GPL/MIT
becausebpf_perf_event_output()
is a GPL-restricted function.