Is there a way to disable the default Sentry integration when we have our own?

Questions / Help
1

We thought we’d use Fly in our load balancer along with some other instances from other clouds. However, we noticed that when we run on Fly it’s not able to reach our normal sentry instance. We have the DSN hardcoded in our codebase, but somehow it’s getting overwritten with the Fly-specific one.

Is there any way to disable this? We can’t use the Fly version since we have services running outside of Fly and already pay for Sentry separately.

2

it might be an env variable coming from a a secret? run fly secrets list to see if there is SENTRY_DSN there, and fly secrets unset it if so.

3

That doesn’t sh ow up in my secrets list. It looks like only the secrets I’ve set myself.