This example uses the admin_config, but that's not important. My question concerns the static_config alternative as well. Continuing with the admin config example, however, if I post this document to the /tap endpoint, it captures traffic:
Possibly this is intentional. After all, I'm tapping at the TCP level, not the HTTP level. But the documentation doesn't say anything about matching (except for "any") not working when tapping at the TCP level. So I don't know if this is a bug or a documentation deficiency.
Transport level tapping doesn't support HTTP matching. I think we can do 2 things here:
1) Better docs
2) Possibly fail if a configuration that we can't actually match on is specified.
I've been experimenting with TCP traffic tapping of an upstream cluster. E.g.,:
This example uses the
admin_config
, but that's not important. My question concerns thestatic_config
alternative as well. Continuing with the admin config example, however, if I post this document to the/tap
endpoint, it captures traffic:But if I post this document, with different match criteria, it never captures traffic, even when the header exists:
Possibly this is intentional. After all, I'm tapping at the TCP level, not the HTTP level. But the documentation doesn't say anything about matching (except for "any") not working when tapping at the TCP level. So I don't know if this is a bug or a documentation deficiency.
I tested with Envoy version