Misclassification of Postgres traffic as Mongo causes missing pgsql data

[ddelnano]

Describe the bug
@srimaln91 and I debugged a situation on their clusters where all postgres traffic is being classified as Mongo. After disabling mongo with the PX_STIRLING_ENABLE_MONGODB_TRACING=0 environment variable, stirling's CONN_TRACE logs show a significant amount of postgres traffic.

Our most recent protocol confusion matrix shows that a small portion of postgres traffic (0.7%) is classified as mongo, but it's clear that our data set is not representative of this case.

To Reproduce
Waiting to confirm what specific traffic causes this misclassification

Expected behavior
Postgres traffic for this case should be visible.

Logs
Waiting to confirm if the logs shared with me are safe to post

App information (please complete the following information):

• Pixie version: v0.14.11
• K8s cluster version: N/A
• Node Kernel version: N/A
• Browser version: N/A