collector/netclass: add master and VRF info metrics - #3765
Open
bewing wants to merge 2 commits into
Open
Conversation
bewing
force-pushed
the
feat/network_info/vrf
branch
from
July 30, 2026 15:00
c029467 to
007589d
Compare
The netlink netclass path already receives IFLA_MASTER and IFLA_LINKINFO in the RTM_GETLINK dump it makes, but exposed neither the master device nor its kind, so there is no way to tell which VRF an interface is in. Add node_network_master_info, labelled with the direct master and the master's kind as reported by IFLA_INFO_SLAVE_KIND, covering VRF membership as well as bridge ports and bond members. Also add node_network_vrf_info to publish the routing table ID of VRF devices. rtnetlink has no vrf driver, so IFLA_VRF_TABLE is decoded from the raw IFLA_INFO_DATA payload. Signed-off-by: Brandon Ewing <brandon.ewing@warningg.com>
Signed-off-by: Brandon Ewing <brandon.ewing@warningg.com>
bewing
force-pushed
the
feat/network_info/vrf
branch
from
July 30, 2026 15:31
007589d to
a665b51
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The netlink netclass path already receives IFLA_MASTER and IFLA_LINKINFO in the RTM_GETLINK dump it makes, but exposed neither the master device nor its kind, so there is no way to tell which VRF an interface is in.
Add node_network_master_info, labelled with the direct master and the master's kind as reported by IFLA_INFO_SLAVE_KIND, covering VRF membership as well as bridge ports and bond members.
Also add node_network_vrf_info to publish the routing table ID of VRF devices. rtnetlink has no vrf driver, so IFLA_VRF_TABLE is decoded from the raw IFLA_INFO_DATA payload.