Improve protocol inference rules #404
Labels
area/datacollector
Issues related to Stirling (datacollector)
kind/feature
New feature or request
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
Pixie’s protocol tracer captures traffic for various protocols, including HTTP, gRPC, postgres and many more. The protocol tracer relies on protocol inference rules to classify traffic based on the contents of the messages being sent.
The protocol inference rules sometimes misclassify traffic, which results in observability gaps.
To validate the accuracy of our protocol inference rules, we need a large database of different traffic patterns (we call this dataset TrafficNet). For this task, we need to (1) expand the TrafficNet data set to include more samples of existing and new protocols, and (2) experiment with different inference models to improve the accuracy of the protocol inference.
The text was updated successfully, but these errors were encountered: