Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve traffic visibility in the data plane #40

Open
guicassolato opened this issue Aug 24, 2023 · 0 comments
Open

Improve traffic visibility in the data plane #40

guicassolato opened this issue Aug 24, 2023 · 0 comments
Labels
enhancement New feature or request target/current
Milestone

Comments

@guicassolato
Copy link

Debugging and obtaining visibility in general on the traffic handled by the wasm module is usually hard. One who tests a Kuadrant policy often has to enable Istio debugging options and scrap from the ingress gateway logs to spot even minor issues such as a typo in a policy. Frequently, Limitador logs are also used in combination.

Neither the path to get those logs enabled, nor the quality of the logs themselves always play much in favour of obtaining such level of visibility. To add the fact that inspecting the ingress gateway for logs (which is not a Kuadrant-owned component) may be counter-intuitive, despite usually the only (best) option.

So much tweaking with hard Istio configs and our own, to debug such a flexible resource as a Kuadrant policy does not seem coherent. IOW, debugging a policy should be we simple and easy as writing one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request target/current
Projects
Status: Todo
Status: No status
Development

No branches or pull requests

2 participants