Naseem

so every request has its own logger instance attached to it `req.log` ... if we set bindings to it, those will be in the onResponse log, or any use of...

Got started on something, is this worth moving forward on? https://github.com/helm/charts/pull/13454

Thanks for the info @kkasravi

> Please re-open this issue @naseemkullah - in [helm/charts#13454 (comment)](https://github.com/helm/charts/pull/13454#issuecomment-523251345), you ceased developing the Helm chart simply due to lack of time. This is a legitimate feature request that someone...

hey @danielbankhead can we move forward with this now? I can make a PR if so, thank you!

Thanks @yurishkuro, could you in the documentation mention any caveats of a multi-region setup where all data is shipped to a single region?

Thanks for explaining that @yurishkuro Finally, as for accessing the various UIs, what do you think is better/what is used at Uber? 1. `jaeger-us-east.uber.com` `jaeger-us-west.uber.com` 2. `jaeger.uber.com/us-east` `jaeger.uber.com/us-west`

I believe this can be closed via https://github.com/DataDog/browser-sdk/pull/1832 which allows browser-sdk to inject w3c context

Hi @drehelis, Worth noting that https://github.com/fluent/helm-charts/blob/32f0fbf5feca821305453890272a4b933cd82835/charts/fluent-bit/templates/daemonset.yaml#L29 should cause the pods to restart upon changes to the configmap, as described in [helm documentation](https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments). Could you confirm if that occurs upon config...