jaeger

Requirement - what kind of business use case are you trying to solve?

Hello team, in PR jaegertracing/jaeger#2798 the tls connection is enabled in collector, it would be good to support configuring cipher for it.

It would be similar to the fluentd tls settings in https://docs.fluentd.org/configuration/transport-section#tls-setting, you can config the ciphers fi

It seems to me that UTC is selected for on the wire representation of time as well as in the database (jaegertracing/jaeger#712), which sort of makes sense, at least with a somewhat naive handling of timezones. However, I think that the Jaeger UI should support displaying times in the timezone local to the user, i.e. of the browser as to reduce the mental load when viewing

The TracerProvider::force_flush method is part of the sdk spec but not the api spec.

I used the ts-migrate script to add @ts-expect-error to silence new TS errors introduced in migration from TypeScript 2.x to 3.x (#907). For example https://github.com/census-instrumentation/opencensus-node/blob/9bd4f114cc3c18f148a2f56392db5e393cb968ab/packages/opencensus-core/src/internal/cls-ah.ts#L95

Definitive list: https://github.com/census-instrum

Use an audit tool such as Polaris and eliminate as many warnings as possible by default for jaeger chart.