-
Notifications
You must be signed in to change notification settings - Fork 367
Description
I wanted to configure Talk to use our Sentry for error reporting. There is no documentation about how to configure Sentry for Talk, but i saw in the code that it is actually integrated and configurable using these ENV vars:
SENTRY_FRONTEND_KEY:
SENTRY_BACKEND_KEY:
I entered my DSN urls here, but nothing shows up in Sentry. I can't find where to set the loglevel, but by default it should be level INFO. If i check the logs on the pod running Talk, i see these logs for example:
{"name":"coral","hostname":"xyz","pid":1,"level":30,"port":abc,"path":"/metrics","msg":"now listening for metrics","time":"2022-03-16T14:01:13.924Z","src":{"file":"/usr/src/app/src/core/server/index.ts","line":331,"func":"process"},"v":0}
I would have expected these logs to appear in Sentry, but they don't.
If i add this line in the sentry.ts file, after the init, i do see the message in Sentry:
Sentry.captureMessage("Something went wrong");
This means Sentry is correctly initialized and configured.
I debugged the options.offlineDebug flag, and it is false in our env, so the FakeDebugTransport is not used.
Expected behavior:
Setting the following ENV vars should enable logging to Sentry:
SENTRY_FRONTEND_KEY:
SENTRY_BACKEND_KEY:
Actual behavior:
Nothing is logged in Sentry
Related Issues:
None
Versions:
- NodeJS: 14
- NPM: 8