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
Currently if you wanna dive into the logs of a certain proxy, you need to go to the log folder and access for example proxy-host-12_error.log or proxy-host-12_access.log. This number 12 comes from the id that the proxy instance is. Which to me is a very arbitrary and hard to spot number. You can only subtly see it if you click on the 3 dots on a proxy, and see the text "Proxy Host #number" there.
I would propose a more semantic name or id that will be used in the logs. For example the domain name, would need much less lookup all the time. Or an added ability that you can give a proxy host a certain name, that is being used for the logs.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently if you wanna dive into the logs of a certain proxy, you need to go to the log folder and access for example proxy-host-12_error.log or proxy-host-12_access.log. This number 12 comes from the id that the proxy instance is. Which to me is a very arbitrary and hard to spot number. You can only subtly see it if you click on the 3 dots on a proxy, and see the text "Proxy Host #number" there.
I would propose a more semantic name or id that will be used in the logs. For example the domain name, would need much less lookup all the time. Or an added ability that you can give a proxy host a certain name, that is being used for the logs.
What do you guys think? :)
Beta Was this translation helpful? Give feedback.
All reactions