Replies: 1 comment 2 replies
-
It does strike me as useful for the script layer to know the interface a node/process is working with. Are you asking because you think it's not useful, or because it's already available elsewhere? I have pondered this in the past from the other end, because it's also mentioned in the Supervisor framework here and here. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Not sure this is an idea, but not sure where else to put it.
Is the
Cluster::Node$interface
something that could be deprecated? In #2841 a bit of discussion happened that it isn't necessarily populated bycluster-layout.zeek
generators today (zeekctl does it though) and things are generally working still as nothing relies on it.Within base, policy/misc/load-balancing does in fact use it, but today we may deprecate the script. Using BPF filters for load-balancing could as well be a package (and have a separate table of workers to interfaces).
@J-Gras pointed at add-interfaces adding interfaces to logs, but that use-cases is probably better handled with the
packet_source()
bif today (and hasn't worked in non-zeekctl environments).Do people think putting a
&deprecated
on it willcause uproar? Happy to cross-post on community.zeek.org.Beta Was this translation helpful? Give feedback.
All reactions