Update docs for the Sentry partnership sunset - #2447
Conversation
New provisioning is blocked platform-wide; the page stays as reference for orgs with existing projects, and the banner points new users at signing up with Sentry directly.
- App handover guide: extension handover is the owner's job; for Sentry that now means the Sentry dashboard directly, since new Fly-provisioned projects are gone - Heroku migration: New Relic row now mirrors the SendGrid keep-using-it advice instead of suggesting fly extensions sentry - Cell-based blueprint: drop the Sentry recommendation sentence - Org roles: Tigris is example enough for extension partners
💡 Codex Reviewdocs/monitoring/sentry.html.md Line 10 in 62e91a6  Remove the disabled provisioning flow
For a reader setting up Sentry after the sunset, this warning is immediately contradicted by the unchanged instructions below: the page still says every Fly organization can claim promotional credits and directs users to run the now-disabled docs/apps/app-handover-guide.html.md Line 54 in 62e91a6 Avoid suggesting an unsupported Sentry project transfer
When an app must be handed to a customer’s separate Sentry organization, the proposed “transfer the project” path is not available in Sentry; projects cannot be moved between organizations. Inviting the customer instead leaves the project in the original Sentry organization, which may also contain projects for the developer’s other apps. Document the actual choices—hand over the existing Sentry organization when it is dedicated to this customer, or create a project in the customer’s organization and update ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Review feedback: the sunset banner was contradicted by the page still telling every org to claim credits and run the disabled create command. The setup section becomes an access section around fly ext sentry dashboard (which still works), and the credits copy moves to past tense.
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c73302519e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Upstash Redis and Tigris already have their own bullets in this list, and Sentry can no longer be freshly provisioned, so the catch-all had nothing left to cover.
|
I have a small preferences for dropping the "same result, one extra step" portion, but outside of that looks great. |
2 participants
New Sentry provisioning is now blocked platform-wide (superfly/web#4239) and removed from the dashboard/launch UIs (superfly/ui-ex#4992, #4993, #4996, #5005). This updates the docs to match:
/docs/monitoring/sentry/: sunset warning banner up top — existing projects keep working, the page stays as reference for them, and new users are pointed at signing up with Sentry directly (same link as the API error message). Rest of the page untouched.fly extensions sentry.Deliberately untouched: the sidebar "Sentry Error Tracking" nav link (the page still serves existing customers) and the python/rust speedrun
fly launchsample outputs (flyctl's own output, will self-correct when flyctl drops the field).Screenshots