Mirrors
/
matrix-public-archive
mirror of https://github.com/matrix-org/matrix-public-archive.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
matrix-public-archive/config/config.default.json

15 lines
551 B
JSON
Raw Normal View History

E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
{
"basePort": "3050",
"basePath": "http://localhost:3050",
"matrixServerUrl": "http://localhost:8008/",
Working e2e test
2022-02-24 02:27:53 -07:00
"archiveMessageLimit": 500,
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 10:08:50 -06:00
"requestTimeoutMs": 25000,
Make the `child_process` error catching more robust (`uncaughtException`) (#51) Split off from https://github.com/matrix-org/matrix-public-archive/pull/43 Listen to `process.on('uncaughtException', ...)` and handle the async errors ourselves so it no longer fails the child process. And if the process does exit with status code 1 (error), we have those underlying errors serialized and shown.
2022-08-29 18:13:56 -06:00
"logOutputFromChildProcesses": false,
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 10:08:50 -06:00
"UNCOMMENT_jaegerTracesEndpoint": "http://localhost:14268/api/traces",
E2E test but still failing because fetching from start of day before test events happened
2022-02-23 20:25:05 -07:00
"testMatrixServerUrl1": "http://localhost:11008/",
"testMatrixServerUrl2": "http://localhost:12008/",
"Secrets": "Remove the 'xxx__' prefix and fill these in your config/config.user-overrides.json or by environment variable",
"xxx__matrixAccessToken": "xxx"
}