-
Notifications
You must be signed in to change notification settings - Fork 4.8k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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
upstream request/response logs #834
Comments
👍 |
another use for this is to see exactly how the request is formed AFTER a transformation and how a response is received BEFORE a transformation |
Is this feature released? |
This would be a great feature. |
Need this to inspect "An invalid response was received from the upstream server" (Status Code 502) |
This is a long shot since this has been open for 3 years but I thought I'd give it a shot since I'm out of ideas. Is there a way to inspect what Kong sends to the upstream server so that I can debug issues with the As the communication happens over SSL and I don't want to install MITM stuff on my own production server I was hoping for a 'cleaner' solution. |
You could consider using Mockbin by Kong |
Actually that makes total sense, dunno why I didn't think of that. Thanks @janv8000 I'll give it a go! |
but how can you use mock bin within-firm boundary, this would be security concerns |
Install and run your own instance: https://github.com/Kong/mockbin#running |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
just like any of the current logging plugins, but to log the actual upstream request and response sent between Kong and the upstream server.
this is useful for debugging upstream requests and identifying issues between Kong and the upstream server, regardless of what is sent back tot he client side.
whether this can be a separate plugin or part of the existing plugins is up for debate.
The text was updated successfully, but these errors were encountered: