uncut thunder
I've enabled the node runtime metrics integration on my application, and it works just fine with the DSN connected to my local system. However, when I deploy my application with a different DSN, I am no longer receiving any node runtime metrics in my Sentry dashboard. What could be going wrong?
I've tried asking Kapa https://discord.com/channels/621778831602221064/1493196622325092503, but it suggested asking for support directly. Let me know what additional info is required here.
fringe saddle
Are you using the SaaS or self-hosted?
Is there any differences on how you deploy your app with running it locally?
Also, can you make sure that the DSN is still valid, looking at your project settings page?
uncut thunder
@fringe saddle Sorry for the late response, we're using the SaaS version of Sentry. The DSN is still valid since we're receiving traces/issues from the deployed env just fine.
fringe saddle
<@406368852847362048> Sorry for the late response, we're using the SaaS version ...
Ah so this is 100% regarding node runtime metrics. Perhaps @regal belfry / @barren jungle might know best?
barren jungle
Hey @uncut thunder Do you get other Sentry data when deploying with the different DSN? I'm not sure why runtime metrics would behave differently here. Any chance the DSN is not available/incorrectly set? In this case you should get no telemetry at all. If you get telemetry but just not runtime metrics, please open a Github issue in https://github.com/getsentry/sentry-javascript
Ah sorry, I should have read your reply more carefully. You already said you receive other telemetry just fine. In this case, please open an issue. Looks like there's a bug we should fix. Thanks 🙂
uncut thunder
Ah alright, I'll put up an issue with some debugging logs