You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We had a really hard time debugging our Redis connection problems, caused by a stray newline in the Tyk helm charts. The problem was made all the harder because Tyk does not show you what configuration it thinks it has when attempting to connect.
Describe the solution you'd like
When setting the log level to DEBUG, include the connection strings used to connect to other services. These should make it much, much easier to debug Redis or other storage connectivity issues.
Describe alternatives you've considered
Tracing the GO redis library to see what it tried to connect to. Not really feasible.
Additional context
Adding validation to the storage config options could help here too; newlines or backslashes are invalid characters in both ip addresses and hostnames, after all.
The text was updated successfully, but these errors were encountered:
I'm Ya'ara, the DX architect in Tyk. Thank you for taking the time to log in this suggestion! Adding more info the logged message as well as validation will definitely improve engineer's life! Improving logs is definitely under my radar ☺️
Is your feature request related to a problem? Please describe.
We had a really hard time debugging our Redis connection problems, caused by a stray newline in the Tyk helm charts. The problem was made all the harder because Tyk does not show you what configuration it thinks it has when attempting to connect.
Describe the solution you'd like
When setting the log level to DEBUG, include the connection strings used to connect to other services. These should make it much, much easier to debug Redis or other storage connectivity issues.
Describe alternatives you've considered
Tracing the GO redis library to see what it tried to connect to. Not really feasible.
Additional context
Adding validation to the storage config options could help here too; newlines or backslashes are invalid characters in both ip addresses and hostnames, after all.
The text was updated successfully, but these errors were encountered: