Skip to content

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

Open
@idanto

Description

@idanto

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions