-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Configure Sentry #3889
Labels
Comments
Hi @jmijn I am a coral user. Have you deployed coral on the sub-directory? Can you please suggest a way to use coral on the sub-dire as 'http://127.0.0.1:5000/${path}' ==> 'http://127.0.0.1:5000/discussions/${path}' |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
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:
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 isfalse
in our env, so theFakeDebugTransport
is not used.Expected behavior:
Setting the following ENV vars should enable logging to Sentry:
Actual behavior:
Nothing is logged in Sentry
Related Issues:
None
Versions:
The text was updated successfully, but these errors were encountered: