We're updating the issue view to help you get more done. 

No path found logs an error

Description

If a client attempts to make a request to a path that does not exist, the framework will throw an exception, which gets logged as an error. In these circumstances, it is not an error in the framework, but an invalid request from a client so it seems like it should not be logged as an error.

For example, if there is no /v2/deploy/status endpoint and a client tries to hit it, the following gets logged:

Release Notes

None

Assignee

Unassigned

Reporter

Albert Shau

Labels

None

Docs Impact

None

UX Impact

None

Priority

Major
Configure