[TT-1525]Invalid user input leads to non critical 'error' log messages

[p4k03n4t0r]

Is your feature request related to a problem? Please describe.
The Tyk API Gateway (and Pump) logs messages including a log level (debug, info, warning, error). Recently we had a production issue after which we decided to add alerting based on the warning and error log level, but this is currently difficult. Wrong user input, for example invalid HMAC authentication, also leads to a error level log message. This way it's hard to decide whether the error level log line is actually an error we will have to act on or it's invalid user input we can ignore.

Describe the solution you'd like
Review the log messages written when the user does a request and change log level depending on whether something is actually broken.

Describe alternatives you've considered
A filter based on the content of the log message. This is a valid solution, we would have to find out which 'error' log messages can be ignored.

Additional context
The ProcessRequest method contains quite some of these 'fake' error log messages.

[Moses-oyedeji]

@p4k03n4t0r Thanks for contacting Tyk!
We apologize for the delayed response. The issue is currently being reviewed and we will keep you updated as soon as we can

[christtyk]

This is quite low priority for us as there are workarounds available

A filter based on the content of the log message. This is a valid solution, we would have to find out which 'error' log messages can be ignored.

Would it help if we provide those error messages in the meantime? We'll keep this open anyway and consider it when we're looking at stories around our logging output