-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[TT-2394] - Detailed Logging - More options of what gets recorded #2362
Comments
Use case:
|
I'm assuming that if we add it to the logging that it would also show up in the debugging tab in the Dashboard as well. Optimally the log would show the entire URL that was forwarded by Tyk to the downstream API. Also the request body for POST, PUT, and PATCH. This would be a useful tool for developing API Rewrite rules. It could be used to show how the URL was rewritten. |
@hoitomt I couldn't agree more. That use case is exactly what brought this feature request. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, please add comments to this ticket if you would like it to stay open. Thank you for your contributions. |
Please keep open. |
This is logged on our product roadmap along with other suggestions around improving the flexibility of analytics; the future direction of Tyk is towards a more rounded observability solution using Open Telemetry, so this may be picked up in that work. |
Do you want to request a feature or report a bug?
Feature
What is the current behavior?
When we activate Detailed Logging, the Gateway stores the header/request/response.
What is the expected behavior?
Be able to select only the parts I want to store and ignore the rest.
The text was updated successfully, but these errors were encountered: