You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a parser stage rejection happens, we need better observability. Ideally, we would have a USDT probe that shows the complete set of parser state transitions that led to the rejection, including the specific rejection point. Right now, one can only look at the packet that got rejected and try to reason through the state machine code manually.
The text was updated successfully, but these errors were encountered:
When a parser stage rejection happens, we need better observability. Ideally, we would have a USDT probe that shows the complete set of parser state transitions that led to the rejection, including the specific rejection point. Right now, one can only look at the packet that got rejected and try to reason through the state machine code manually.
The text was updated successfully, but these errors were encountered: