YueGuobin 9262dcfaef

fix: normalize marker.match event tag to int to match the REST schema ...

The WS event carried the tag as str (verbatim from the MARK signal) when
present and as int when falling back to the registry, so one tag reached
consumers as two different values. Parse the signal's decimal (the exact
value we installed via 'mark <bpf> tag <id>') and keep the registered int
on malformed input; None only when neither side carries one.

2026-09-05 21:49:24 +08:00

..

__init__.py

feat: implement traffic insight marker backend (ubridge mark filter)

2026-07-16 00:39:51 +08:00

marker_listener.py

fix: normalize marker.match event tag to int to match the REST schema

2026-09-05 21:49:24 +08:00

marker_manager.py

log: suppress marker sink stats when no matches received

2026-08-11 11:43:43 +08:00