Some questions about using vike-react-sentry #3149
Unanswered
MrNaif2018
asked this question in
Discussion
Replies: 2 comments 4 replies
-
|
CC @nitedani (author of |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@MrNaif2018 Both Dani and myself are quite busy with high priorirties — would you be up to fork |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! Thank you so much for all the great work you do! I've been trying the new vike-react-sentry integration and have some questions
First of all, it seems to require
PUBLIC_ENV__SENTRY_DSNeven if I configured it differently in+sentry.ts(or most likely, it seems to disallow it when it seesSENTRY_DSNin env files).My +sentry.ts:
So I noticed multiple things: even if I make my
SENTRY_DSNvalue based onSENTRY_DSNand notPUBLIC_ENV_SENTRY_DSN, it tells:Error: [vike-react-sentry] SENTRY_DSN is not supported. Use PUBLIC_ENV__SENTRY_DSN instead, or set dsn in your sentry config.Maybe that is intentional, it's just that for me in my backend projects we just name it
SENTRY_DSNand that's it (:(that again relates to #3146 and ability to customize public prefix/not use
PUBLIC_ENV__things)Also, if I set integrations array, from my understanding https://github.com/vikejs/vike-react/blob/029427a70510b2989a79d398a90f69190a00f749/packages/vike-react-sentry/src/integration/onCreateGlobalContext.client.ts#L29 those integrations would get removed?
I see it uses a different list of integrations on client and server. And not sure, if I e.g. enable
consoleLoggingIntegrationbut also wantbrowserTracingIntegrationand replay integration, would I need to add those too? And if yes, would that cause any issues that before it was set only on server for example, and on client it was not set.Another issue I met was
Error: [vike-react-sentry] Sentry DSN is required. Set PUBLIC_ENV__SENTRY_DSN env var, or set dsn in the sentry config.So if extension is enabled, it requires it always. I would say when sentry dsn is set it can activate itself makes more sense. But+sentry.tsfile is most likely needed anyway, so probably I need to do something likeenabled: !!env.SENTRY_DSNin that fileAnother issue I stumbled upon is, it looks like
+sentry.tsfile is being loaded 3 times: during config loading even before vite begins to run, on server and on clientso if I do
import { env } from "@/env"it tells
And the main weird issue: I seem to get 429 too many requests from sentry 🤔
I know I've set traces sample rate to 1.0, but it indeed seems to spam too many, and even on 1.0 shouldn't it work and not give 429? 🤔
The main thing I noticed was, when I was scrolling my page back and forth, each time it told
Even though I was on the same page, so maybe it was part of the reason
Also here's the full log on a fresh ip address from page load to sentry rate limit:
Details
Beta Was this translation helpful? Give feedback.
All reactions