Skip to content
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

Should gateway logs be scoped to service name for logged in user? #297

Open
Marak opened this issue Oct 29, 2017 · 0 comments
Open

Should gateway logs be scoped to service name for logged in user? #297

Marak opened this issue Oct 29, 2017 · 0 comments

Comments

@Marak
Copy link
Collaborator

Marak commented Oct 29, 2017

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.

Requires more investigation. Medium-low priority.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant