-
Couldn't load subscription status.
- Fork 1.2k
[doc]: Refactor netlink message for high frequency telemetry #2064
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
base: master
Are you sure you want to change the base?
Conversation
|
/azp run |
|
No pipelines are associated with this pull request. |
Signed-off-by: Ze Gan <[email protected]>
|
/azp run |
|
No pipelines are associated with this pull request. |
| --- | ||
| title: Netlink message structure | ||
| --- | ||
| packet-beta |
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.
packet-data ?
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.
Here is 'packet-beta' that is a flag of mermaid. https://docs.mermaidchart.com/mermaid-oss/syntax/packet.html
Signed-off-by: Ze Gan <[email protected]>
|
/azp run |
|
No pipelines are associated with this pull request. |
This pull request refines the documentation and sample code for transmitting IPFIX telemetry data over netlink messages. The changes clarify the netlink message structure, provide a visual breakdown, and update the kernel-side sample code to directly append IPFIX data as payload without extra netlink attributes.
Documentation improvements:
Sample code updates: