Collect Metrics about meridio HOT 2 OPEN

meridio.interface.METRIC_TYPE (Planned):

• Which interfaces is more precisely included here: Proxy interfaces? Application pod interfaces? FE external interface?
• Is IPv4 and IPv6 interface counters to be included? I guess the proposal is to have L2 counters.
• How is the traffic on this interface to be mapped to counters on NSM/infra/SNIA level? by using MAC-addresses?

meridio.conduit.stream.status (Planned):

• What would be the status presented here?

meridio.conduit.stream.flow.matches:

• It would be nice to a have counter for non-matched packet, or maybe a counter for the total number of packets handled.

meridio.conduit.stream.target.packet.hits (Planned)

• How can packets towards a target be mapped to the interface used for sending the traffic onwards.

meridio.conduit.stream.target.latency (Planned)

• Do this require some test-traffic injected internally?
• What results could be seen? And how to interpret these results in a general fashion?

meridio.attractor.gateway.status (Planned)

• Is the proposal to have a up/down indication? It could be nice to have this both for BGP and BFD separately.
• Besides this number of learned BGP routes could be of interest.
• Number of sent/received BFD and BGP packets/bytes to get a clearer view on the "real payload"
  (yes, there can be other kinds traffic such ARP, but still... )

from meridio.

for non-matched packets, nolb_fwmark in nfqlb could be used to blackhole traffic in policy route and then counting in the same way as the targets using nftables

from meridio.