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

Logs: Better debug logs in case of unhandled route by the middleware #912

Open
idanto opened this issue Aug 19, 2024 · 0 comments
Open

Logs: Better debug logs in case of unhandled route by the middleware #912

idanto opened this issue Aug 19, 2024 · 0 comments

Comments

@idanto
Copy link

idanto commented Aug 19, 2024

As a follow-up to this Discord thread

In this log line

the actual URL that has been called is not related to the API Gateway
This will be true for any other call to any other API we add to our BE that is not being used with the API gateway path.

It is true that the API gateway stripped out this prefix path, but when I look at this from a system monitoring perspective, this log indicates that someone called the service with this path, which is not true in this case or in any case (Even when the API gateway calls this service, it is not with this prefix)

If you want to help debug here, I suggest logging the actual path being called with some headers (maybe user agents and a few others) and the IP that can help indicate who the caller is.

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

No branches or pull requests

1 participant