The current behavior is that all logs for hot-code gateway requests are sent to a special logging endpoint.
If there is no session, gateway logs are scoped to anonymous user. That makes sense.
If there is a session, gateway logs are scoped to current user, but are not scoped to any particular service. This can be counter-intuitive when attempting to develop services using the code editor.
We should consider whether or not logs for the gateway should be scoped to the specific service being edited at the time. I think the best solution will probably be making the gateway logging behavior configurable and have it default to fully scoped when users are logged in editing services on the /admin page.
The current behavior is that all logs for hot-code gateway requests are sent to a special logging endpoint.
If there is no session, gateway logs are scoped to
anonymoususer. That makes sense.If there is a session, gateway logs are scoped to current user, but are not scoped to any particular service. This can be counter-intuitive when attempting to develop services using the code editor.
We should consider whether or not logs for the gateway should be scoped to the specific service being edited at the time. I think the best solution will probably be making the gateway logging behavior configurable and have it default to fully scoped when users are logged in editing services on the
/adminpage.Requires more investigation. Medium-low priority.