Eric Eastwood ddfe94beab OpenTelemetry tracing so we can see spans where the app is taking time (#27) ... OpenTelemetry tracing so we can see spans where the app is taking time. For the user, we specifically show the spans for the external API HTTP requests that are slow (so we know when the Matrix API is being slow). Enable tracing: - `npm run start -- --tracing` - `npm run start-dev -- --tracing` What does this PR change: - Adds OpenTelemetry tracing with some of the automatic instrumentation (includes HTTP and express) - We ignore traces for serving static assets (just noise) - Adds `X-Trace-Id` to the response headers - Adds `window.tracingSpansForRequest` which includes the external HTTP API requests made during the request - Adds a fancy 504 timeout page that includes trace details and lists the slow HTTP requests - Adds `jaegerTracesEndpoint` configuration to export tracing spans to Jaeger - Related to, https://github.com/matrix-org/matrix-public-archive/issues/26		2022-07-14 11:08:50 -05:00
..
config.default.json	OpenTelemetry tracing so we can see spans where the app is taking time (#27)	2022-07-14 11:08:50 -05:00
config.test.json	E2E test but still failing because fetching from start of day before test events happened	2022-02-23 21:25:05 -06:00