Feature Request: Log Improvements about featurehub HOT 4 OPEN

I think in addition to what @cspalding requested, having consistent request ids across different components would really help to track down how they are interacting (or not).

from featurehub.

Heya - so a few things I can think of for these points.

1. Once the jersey tracing is turned on, the entire request and response content (all headers and body both received and sent) is actually put directly into the logs. Only the auth token is obfuscated. I presume the issue is that you don't want the req/response for successful requests only failed ones? This is quite difficult as we don't cache the full body of the incoming request waiting for the outgoing response, as that can be potentially dangerous in terms of denial of service. The other option is OpenTelemetry? Any suggestions that would make it easier are welcome here!

2. Clearer understanding of the error is probably best on a case by case basis, could you perhaps list some of the errors you are seeing so we can address those? We already have another ticket for addressing the errors in OAuth2 that people are seeing but any input from your team as to the errors would be helpful in making the logging more useful to people!

3. We use OpenTelemetry and wrap everything in OpenTelemetry support, so "request ids" (i.e. traceids) are already being used across the entire ecosystem. We don't surface OpenTracing trace contexts in the logs however, nor any extra W3C Baggage. You don't normally put these in your logs because they represent spans, and so there is no consistent way to track them by just looking at logs alone. We could add a request id to the baggage and endeavour to log baggage would that be of use?

from featurehub.

I have added in support for fields from the OTEL baggage into the logs for this to allow cross thread tracking and delivery across the different services. I will be adding it to the UI as well as part of the next update. As I'm not getting more explicit feedback I will leave it at that and close the ticket once those are in.

from featurehub.

I'll be closing this out on the next release with this piece of doc added: fad1c04

from featurehub.