Skip to content

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

Closed
ahmadnassri opened this issue Jan 4, 2016 · 10 comments
Closed

upstream request/response logs #834

ahmadnassri opened this issue Jan 4, 2016 · 10 comments
Labels
task/feature Requests for new features in Kong

Comments

@ahmadnassri
Copy link
Contributor

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.

@sonicaghi
Copy link
Member

👍

@ahmadnassri
Copy link
Contributor Author

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

@ahmadnassri ahmadnassri changed the title upstream requests logs upstream request/response logs Jan 5, 2016
@thibaultcha thibaultcha added the task/feature Requests for new features in Kong label Jan 8, 2016
@ahmadnassri ahmadnassri added the BC label May 13, 2016
@thibaultcha thibaultcha removed the BC label Sep 1, 2016
@jsettypalli
Copy link

Is this feature released?

@jmgpeeters
Copy link

This would be a great feature.

@cocktailkrabbe
Copy link

Need this to inspect "An invalid response was received from the upstream server" (Status Code 502)

@somada141
Copy link

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 request-transformer plugin?

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.

@janv8000
Copy link

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 request-transformer plugin?

You could consider using Mockbin by Kong

@somada141
Copy link

Actually that makes total sense, dunno why I didn't think of that. Thanks @janv8000 I'll give it a go!

@justlife787
Copy link

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 request-transformer plugin?

You could consider using Mockbin by Kong

but how can you use mock bin within-firm boundary, this would be security concerns

@janv8000
Copy link

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

@guanlan guanlan closed this as completed May 26, 2021
@Kong Kong locked and limited conversation to collaborators May 26, 2021

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
task/feature Requests for new features in Kong
Projects
None yet
Development

No branches or pull requests