jaeger

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

Actual the windows executables (jaeger-agent.exe, jaeger-collector.exe, ...) don't have a version set. It is hard to identify the current used version and check if the actual used version is outdated.

Probl

The recently added flags in timescale/promscale#578 are yet to be updated in prom-migrator's readme which can be found here.

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

See the spec change for details open-telemetry/opentelemetry-specification#1269

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.