Closed Bug 1780250 Opened 3 years ago Closed 3 years ago

Migrate Sentry DSN to point to cloud Sentry

Categories

(Conduit :: Lando, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: sheehan, Assigned: sheehan)

Details

We need to migrate the Sentry DSN to point to the SaaS Cloud Sentry instead of the soon-to-be-deprecated Mozilla-hosted Sentry. This needs to be completed for Lando-api and lando-ui on both dev and prod.

As the Sentry instance we're pointing at will be turned off at the end of this month the updated SENTRY_DSN needs to be deployed soon.

Severity: -- → S2
Flags: needinfo?(zeid)
Flags: needinfo?(zeid)

DSN's have been updated from Ops' POV. We have deployed the API to pick up these changes but need to deploy UI as well.

UI hasn't been deployed as there are changes on the main branch we don't want to be visible just yet. I'll hide those changes but keep the functionality so we can resolve this bug.

Assignee: nobody → sheehan

dlactin, we've deployed lando-api a few times now and still don't see data showing up in the new Sentry instance. Can you check if this has been deployed properly on your side?

Flags: needinfo?(dlactin)

Looks like I missed pushing the prod DSN updates after dev testing.

The sentry DSN has now been updated for lando-ui and lando-api prod. The next deployment will use the new sentry configuration.

Flags: needinfo?(dlactin)

We've made deploys to api/ui on both dev and prod. I don't see any events in Sentry just yet but we should have everything in place.

(In reply to Connor Sheehan [:sheehan] from comment #5)

We've made deploys to api/ui on both dev and prod. I don't see any events in Sentry just yet but we should have everything in place.

Nevermind, we need to deploy lando-api since dlactin's changes. We landed code in the repo but haven't deployed it. I'll do this tomorrow.

Both API and UI are deployed on dev and prod.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.