Open anar-khalilov opened 1 year ago
We would be super happy to receive feedback about this one because this is really important for us.
Hi @anar-khalilov, thanks for your PR.
I can understand your need to not log all downstream requests, we'll have to consider a general solution rather than one that just fits your use case though.
Are you ok running a fork for now while we consider this?
Things to consider:
error
should be for gateway errors, not downstream responses, so perhaps warning
makes more senseThanks for comprehensive response. We are currently unable to run a fork due to corporate policies. Because of that we are wondering if this issue has been planned/started etc.
Hi @anar-khalilov, it's not on our roadmap yet. If you are unable to run a fork, are you able to put a filter in your log collection that drops the unneeded records?
https://github.com/movio/bramble/pull/179
Currently, all requests are being logged as Info (v1.4.3/instrumentation.go:56) and it really results in lots and lots of logs, hence increases costs for our applications.
As per our application's requirements, we don't want to see logs for HTTP200 responses.
What we would like to achieve is to log depending on the
response.status
value like below.However, if you come up with a better idea, we are welcome to use it.