mirror of
https://github.com/supabase/supabase.git
synced 2026-10-06 09:55:06 +03:00
e0280cb650
<!-- CURSOR_AGENT_PR_BODY_BEGIN --> ## Stack Draft stack extracted from `docs/monitoring`. Merge bottom-up. The troubleshooting *catalog* rewrite (`content/troubleshooting` and the Diagnosing UI) stays out of scope. 1. #49503 move inspect and advisors 2. #49501 split Studio logs from ClickHouse queries 3. #49500 treat reports as signal dashboards 4. #49502 add Observe the data hub 5. #49506 add agent setup components 6. #49504 add hire-an-agent templates 7. **#49505** restructure observability nav, overview, Detecting, and flatten Observe the data ← **this PR** ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update. Top layer in the observability stack. ## What is the current behavior? The section is still titled Monitoring and Debugging, with a Debugging / Monitoring split that does not match the new pages. The debugging guide is still the master layer-isolation + symptom table. Observe the data is split into “what data” vs “where to observe it,” which duplicates the source pages. ## What is the new behavior? - Section title is Observability - Overview groups Observe the data, Detect and resolve, Hire an agent, and Export - **Observe the data is flattened by source.** Logs, Metrics API, Database, Advisors, and Reports each list where to read that source. There is no separate MCP/API/CLI/Studio nav group. - **Observe vs Detecting:** Observe is the catalog (what exists, how to access it). Detecting is how to *use* those sources to pick up a Health / Security / Performance / Usage signal. Named errors skip to Diagnosing. - Studio Logs sits under Logs. Reports sits beside the other sources. - Troubleshooting stays in the global menu and also appears as Diagnosing under Detect and resolve ## Additional context This is the last PR in the stack. Together the seven PRs reconstruct the `docs/monitoring` observability IA and guide content, without shipping the troubleshooting catalog overhaul. <!-- CURSOR_AGENT_PR_BODY_END --> <div><a href="https://cursor.com/agents/bc-a3cb5ece-925b-4046-b58a-5d69e9a9d794?cursor_ref=pr_footer&cursor_cta=open_in_web"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-web-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-web-light.png"><img alt="Open in Web" width="114" height="28" src="https://cursor.com/assets/images/open-in-web-dark.png"></picture></a> <a href="https://cursor.com/background-agent?bcId=bc-a3cb5ece-925b-4046-b58a-5d69e9a9d794&cursor_ref=pr_footer&cursor_cta=open_in_cursor"><picture><source media="(prefers-color-scheme: dark)" srcset="https://cursor.com/assets/images/open-in-cursor-dark.png"><source media="(prefers-color-scheme: light)" srcset="https://cursor.com/assets/images/open-in-cursor-light.png"><img alt="Open in Cursor" width="131" height="28" src="https://cursor.com/assets/images/open-in-cursor-dark.png"></picture></a> </div> --------- Co-authored-by: Cursor Agent <cursoragent@cursor.com> Co-authored-by: Saxon Fletcher <SaxonF@users.noreply.github.com> Co-authored-by: Nik Richers <nik@validmind.ai>
60 lines
3.0 KiB
Plaintext
60 lines
3.0 KiB
Plaintext
---
|
||
id: 'project-transfer'
|
||
title: 'Project Transfers'
|
||
description: 'Transfer a project to another organization.'
|
||
---
|
||
|
||
You can freely transfer projects between different organizations. Head to your [projects' general settings](/dashboard/project/_/settings/general) to initiate a project transfer.
|
||
|
||
<Image
|
||
alt="Project Transfer: General Settings"
|
||
src={{
|
||
light: '/docs/img/guides/platform/project-transfer-overview--light.png',
|
||
dark: '/docs/img/guides/platform/project-transfer-overview.png',
|
||
}}
|
||
className="max-w-[600px] mx-auto! border rounded-md"
|
||
|
||
width={677}
|
||
height={224}
|
||
/>
|
||
|
||
<Image
|
||
alt="Project Transfer: Confirmation Modal"
|
||
src={{
|
||
light: '/docs/img/guides/platform/project-transfer-modal--light.png',
|
||
dark: '/docs/img/guides/platform/project-transfer-modal.png',
|
||
}}
|
||
className="max-w-[600px] mx-auto!"
|
||
|
||
width={773}
|
||
height={581}
|
||
/>
|
||
|
||
Source organization - the organization the project currently belongs to
|
||
Target organization - the organization you want to move the project to
|
||
|
||
## Pre-Requirements
|
||
|
||
- You need to be the owner of the source organization.
|
||
- You need to be at least a member of the target organization you want to move the project to.
|
||
- No active GitHub integration connection
|
||
- No project-scoped roles pointing to the project (Team/Enterprise plan)
|
||
- No log drains configured
|
||
|
||
## Usage-billing and project add-ons
|
||
|
||
For usage metrics such as disk size, egress or image transformations and project add-ons such as [Compute Add-On](/docs/guides/platform/compute-and-disk), [Point-In-Time-Recovery](/docs/guides/platform/backups#point-in-time-recovery), [IPv4](/docs/guides/platform/ipv4-address), [Log Drains](/docs/guides/observability/log-drains), [Advanced MFA](/docs/guides/auth/auth-mfa/phone) or a [Custom Domain](/docs/guides/platform/custom-domains), the source organization will still be charged for the usage up until the transfer. The charges will be added to the invoice when the billing cycle resets.
|
||
|
||
The target organization will be charged at the end of the billing cycle for usage after the project transfer.
|
||
|
||
## Things to watch out for
|
||
|
||
- Transferring a project might come with a short 1-2 minute downtime if you're moving a project from a paid to a Free Plan.
|
||
- You could lose access to certain project features depending on the plan of the target organization, i.e. moving a project from a Pro Plan to a Free Plan.
|
||
- When moving your project to a Free Plan, we also ensure you’re not exceeding your two free project limit. In these cases, it is best to upgrade your target organization to Pro Plan first.
|
||
- You could have less rights on the project depending on your role in the target organization, i.e. you were an Owner in the previous organization and only have a Read-Only role in the target organization.
|
||
|
||
## Transfer to a different region
|
||
|
||
Note that project transfers are only transferring your projects across an organization and cannot be used to transfer between different regions. To move your project to a different region, see [migrating your project](/docs/guides/platform/migrating-within-supabase).
|