mirror of
https://github.com/supabase/supabase.git
synced 2026-10-16 22:59:11 +03:00
Bring over the images
This commit is contained in:
dshukertjr committed
1 parent
6a7f7575cd
commit
f3cbdaa822
90 files changed
+66
-110
No files matched your search
Binary file not shown.
|
After Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 171 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 53 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 737 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 111 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 225 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 101 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 227 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 89 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 92 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 97 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 81 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 109 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 29 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 105 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 124 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 136 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 63 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 51 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 99 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 94 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 20 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 61 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 47 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 130 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 21 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 7.0 MiB |
Binary file not shown.
|
After Width: | Height: | Size: 125 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 113 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 170 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 143 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 57 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 11 KiB |
BIN
Binary file not shown.
|
After Width: | Height: | Size: 171 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 81 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 52 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 75 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 50 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 331 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 44 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 68 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 40 KiB |
Binary file not shown.
|
After Width: | Height: | Size: 17 MiB |
@@ -16,7 +16,7 @@ You can review the [Billing Dashboard](/dashboard/org/_/usage#egress) for egress
|
||||
|
||||
- Example: [Custom Reports](/dashboard/project/_/observability/api-overview?newReport=true) -> Add/Remove charts -> Database API -> API Egress.
|
||||
|
||||
|
||||
|
||||
|
||||
## What is contributing to Egress?
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ Work through the following steps to diagnose and repair your migration history s
|
||||
1. Go to [Branches](/dashboard/project/_/branches) and find the affected branch.
|
||||
2. Click **View logs**. A dialog shows the branch's creation workflow, including the failed step.
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
@@ -25,7 +25,7 @@ Work through the following steps to diagnose and repair your migration history s
|
||||
2. Look for entries beginning with `execute <unnamed>:`. These are the individual migration statements being replayed.
|
||||
3. Find the entry marked as an **error**, which the Dashboard also highlights in red. This is the statement that failed, and its message explains why. Common messages include relation already exists, column not found, permission denied, and relation does not exist.
|
||||
|
||||
|
||||
|
||||
|
||||
---
|
||||
|
||||
@@ -66,7 +66,7 @@ This retrieves the migration files currently recorded against your `main` branch
|
||||
|
||||
After repairing the migration history, either create a new branch or **rebase** the existing affected branch.
|
||||
|
||||
|
||||
|
||||
|
||||
Check the branch's workflow logs again, as described in step 1, to confirm migrations now complete successfully.
|
||||
|
||||
|
||||
+1
-1
@@ -10,7 +10,7 @@ PostgREST supports 2 config parameters:
|
||||
- Exposed Schemas
|
||||
- Extra Search Path
|
||||
|
||||
|
||||
|
||||
|
||||
You do not need to add your "security definer" Functions to either of these if you are using them in your Policies.
|
||||
|
||||
|
||||
@@ -126,7 +126,7 @@ Your project uses the [new asymmetric keys](/blog/jwt-signing-keys) for authenti
|
||||
|
||||
In the [Functions Dashboard](/dashboard/project/_/functions/), open the affected function's `detail tab` and toggle off JWT verification.
|
||||
|
||||
|
||||
|
||||
|
||||
#### Method B: Supabase CLI
|
||||
|
||||
|
||||
@@ -58,7 +58,7 @@ The difference between the two errors is:
|
||||
> [!NOTE]
|
||||
> Always configure an appropriate time frame when querying the logs
|
||||
>
|
||||
> 
|
||||
> 
|
||||
|
||||
You cannot inspect the function dashboard to find platform 404 errors, instead, run the below query in the [SQL Editor](/dashboard/project/_/sql/new?skip=true&source=logs&content=select%20distinct%0A%20%20log_attributes%5B%27request.pathname%27%5D%20as%20function_name%2C%0A%20%20log_attributes%5B%27response.status_code%27%5D%20as%20status_code%2C%0A%20%20case%0A%20%20%20%20when%20log_attributes%5B%27execution_id%27%5D%20%3D%20%27%27%20then%20%27FUNCTION_NOT_FOUND%27%0A%20%20%20%20else%20%27FUNCTION%20RECOGNIZED%3A%20custom%20404%20message%20in%20app%20logic%27%0A%20%20end%20as%20type_of_404%0Afrom%20logs%0Awhere%0A%20%20source%20%3D%20%27function_edge_logs%27%0A%20%20and%20toInt32OrZero%28log_attributes%5B%27response.status_code%27%5D%29%20%3D%20404%0Alimit%2010%3B). The results show all requests that reached Supabase but were rejected as unrecognizable.
|
||||
|
||||
@@ -90,7 +90,7 @@ In your code, make sure your function name doesn't have any typos, such as:
|
||||
|
||||
When selecting your function in the [Function Dashboard](/dashboard/project/_/functions), you should have the option to make a test call:
|
||||
|
||||
|
||||
|
||||
|
||||
If the call works, consider double checking your code for typos or to see if it is overwriting the function name dynamically. Otherwise, go on to step 4.
|
||||
|
||||
@@ -100,7 +100,7 @@ If step 3 fails, it may be a sign of an internal bug and it may be necessary to
|
||||
|
||||
This can be done within the [Function Dashboard](/dashboard/project/_/functions) under the respective function's code tab:
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, if you develop locally, you can redeploy the function with the [Supabase CLI](/docs/guides/local-development/cli/getting-started?queryGroups=platform&platform=macos):
|
||||
|
||||
|
||||
@@ -85,7 +85,7 @@ A [`SyntaxError`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refere
|
||||
|
||||
In the [Function Dashboard](/dashboard/project/_/functions), under the affected function's `Log` tab, you can filter for the key phrase `worker boot error:`. the log will tell you syntax error occurred:
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, instead of using the Function Dashboard, you can programmatically find boot failure error messages in the [SQL Editor](/dashboard/project/_/sql/new?skip=true&source=logs&content=select%0A%20%20fl.event_message%2C%0A%20%20fl.timestamp%2C%0A%20%20fel.function_name%2C%0A%20%20fel.status_code%0Afrom%0A%20%20%28%0A%20%20%20%20select%0A%20%20%20%20%20%20timestamp%2C%0A%20%20%20%20%20%20event_message%2C%0A%20%20%20%20%20%20log_attributes%5B%27function_id%27%5D%20as%20function_id%2C%0A%20%20%20%20%20%20log_attributes%5B%27version%27%5D%20as%20version%0A%20%20%20%20from%20logs%0A%20%20%20%20where%20source%20%3D%20%27function_logs%27%0A%20%20%20%20%20%20and%20log_attributes%5B%27event_type%27%5D%20%3D%20%27BootFailure%27%0A%20%20%29%20as%20fl%0A%20%20left%20join%20%28%0A%20%20%20%20select%0A%20%20%20%20%20%20log_attributes%5B%27function_id%27%5D%20as%20function_id%2C%0A%20%20%20%20%20%20log_attributes%5B%27version%27%5D%20as%20version%2C%0A%20%20%20%20%20%20log_attributes%5B%27request.pathname%27%5D%20as%20function_name%2C%0A%20%20%20%20%20%20log_attributes%5B%27response.status_code%27%5D%20as%20status_code%0A%20%20%20%20from%20logs%0A%20%20%20%20where%20source%20%3D%20%27function_edge_logs%27%0A%20%20%29%20as%20fel%20on%20fl.function_id%20%3D%20fel.function_id%20and%20fl.version%20%3D%20fel.version%0Aorder%20by%20fl.timestamp%2C%20fel.function_name%0Alimit%2020%3B) with the below query:
|
||||
|
||||
|
||||
@@ -57,7 +57,7 @@ console.timeEnd('fetch-user-data')
|
||||
|
||||
The time response will show up in the [function's dashboard](/dashboard/project/_/functions) under the `Log` tab with the label you assigned it. You can use the label as a keyword to search for the timestamp.
|
||||
|
||||
|
||||
|
||||
|
||||
For local development, you can also step through execution with [Chrome Dev Tools](/docs/guides/functions/debugging-tools).
|
||||
|
||||
|
||||
@@ -42,7 +42,7 @@ In the [function dashboard's](/dashboard/project/_/functions/) `Logs` tab, you c
|
||||
- `Memory limit exceeded`
|
||||
- `CPU Time exceeded`
|
||||
|
||||
|
||||
|
||||
|
||||
Alternatively, you can filter for the specific errors from the function using the [SQL Editor](/dashboard/project/_/sql/new?skip=true&source=logs&content=select%0A%20%20fl.event_message%2C%0A%20%20fl.timestamp%2C%0A%20%20fel.function_name%2C%0A%20%20fel.status_code%0Afrom%0A%20%20%28%0A%20%20%20%20select%0A%20%20%20%20%20%20timestamp%2C%0A%20%20%20%20%20%20event_message%2C%0A%20%20%20%20%20%20log_attributes%5B%27execution_id%27%5D%20as%20execution_id%0A%20%20%20%20from%20logs%0A%20%20%20%20where%20source%20%3D%20%27function_logs%27%0A%20%20%20%20%20%20and%20log_attributes%5B%27level%27%5D%20%3D%20%27error%27%0A%20%20%29%20as%20fl%0A%20%20inner%20join%20%28%0A%20%20%20%20select%0A%20%20%20%20%20%20log_attributes%5B%27execution_id%27%5D%20as%20execution_id%2C%0A%20%20%20%20%20%20log_attributes%5B%27request.pathname%27%5D%20as%20function_name%2C%0A%20%20%20%20%20%20log_attributes%5B%27response.status_code%27%5D%20as%20status_code%0A%20%20%20%20from%20logs%0A%20%20%20%20where%20source%20%3D%20%27function_edge_logs%27%0A%20%20%20%20%20%20and%20toInt32OrZero%28log_attributes%5B%27response.status_code%27%5D%29%20%3D%20546%0A%20%20%29%20as%20fel%20on%20fl.execution_id%20%3D%20fel.execution_id%0Aorder%20by%20fl.timestamp%2C%20fel.function_name%0Alimit%2020%3B)
|
||||
|
||||
@@ -171,7 +171,7 @@ limit 24;
|
||||
```
|
||||
|
||||
The output may look like:
|
||||
|
||||
|
||||
|
||||
If the failures are concentrated to a specific time, you can check if you made any updates around that period or if users were engaging in atypical behavior, such as sending larger payloads.
|
||||
|
||||
|
||||
+2
-6
@@ -7,14 +7,10 @@ github_url: 'https://github.com/orgs/supabase/discussions/17296'
|
||||
|
||||
Although Failed to Fetch can occur for a variety of reasons a common one in the dashboard or when using update code is related to a browser extension.
|
||||
|
||||
|
||||
|
||||
|
||||
https://chrome.google.com/webstore/detail/allow-cors-access-control/lhobafahddgcelffkeicbaginigeejlf
|
||||
|
||||
This extension sets PATCH to be blocked by default for some reason...
|
||||
|
||||
<img
|
||||
width="704"
|
||||
alt="168501713-5f020510-4555-4cc3-84de-582efc1c62de"
|
||||
src="https://github.com/supabase/supabase/assets/54564956/c61b9292-2954-4c68-8129-995941f36210"
|
||||
/>
|
||||
|
||||
+1
-1
@@ -4,7 +4,7 @@ description: 'Explains that this error typically means the database is overloade
|
||||
topics: ['Troubleshooting', 'Database', 'Dashboard']
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
This error typically happens when the database is overloaded and causing an outage. As the database does not respond in a timely manner there can be a variety of symptoms such as tables not loading, error messages related to retrieving data and the dashboard seems to be unresponsive.
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ curl https://<YOUR_PROJECT_REF>.supabase.co/customer/v1/privileged/metrics --use
|
||||
|
||||
## Step 2: Set your Grafana Dashboard to auto-refresh in the top right corner
|
||||
|
||||
|
||||
|
||||
|
||||
## Step 3: Make sure your docker container has the default configurations
|
||||
|
||||
@@ -29,7 +29,7 @@ docker ps -f name=supabase-grafana
|
||||
|
||||
The output should look something like this:
|
||||
|
||||
|
||||
|
||||
|
||||
Here it is in an easier to read format
|
||||
|
||||
|
||||
@@ -22,7 +22,7 @@ Moreover, your instance might not be able to handle future traffic spikes if it
|
||||
|
||||
You can check your CPU usage directly on the Supabase Platform. For this go to database health in the [Observability section](/dashboard/project/_/observability/database) and select your project.
|
||||
|
||||
|
||||
|
||||
|
||||
It is also possible to monitor your resources and set up alerts using Prometheus/Grafana. You can find a guide for this [here](/docs/guides/observability/metrics).
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ The default connection values are set based on a solid understanding of Postgres
|
||||
|
||||
This is a Grafana Chart of unhealthy memory usage:
|
||||
|
||||
|
||||
|
||||
|
||||
- Yellow: represents active memory
|
||||
- Red: represents SWAP, which is disk storage that the system treats as if it were memory
|
||||
@@ -91,12 +91,8 @@ select
|
||||
|
||||
The below chart is an example of what can occur to the CPU if 100s of connections are inappropriately opened/closed every second or many CPU intensive queries are run in parallel
|
||||
|
||||
|
||||
|
||||
|
||||
If you plan on increasing your direct connection numbers, your database should have relatively predictable or low CPU usage, such as what the example displays below:
|
||||
|
||||
<img
|
||||
width="706"
|
||||
alt="Screenshot 2024-06-11 at 3 09 03 PM"
|
||||
src="https://github.com/supabase/supabase/assets/91111415/ee3e4f4c-87a1-4ef8-9ca5-af9094fc1b93"
|
||||
/>
|
||||
|
||||
@@ -16,7 +16,7 @@ This method requires two steps - first delete in Supabase, then clean up in Verc
|
||||
|
||||
Go to your [project settings](/dashboard/project/_/settings/general) and click **"Delete project"**. This permanently removes your database and marks it as "uninstalled" in Vercel.
|
||||
|
||||
|
||||
|
||||
|
||||
2. **Clean up in Vercel**
|
||||
|
||||
@@ -25,13 +25,13 @@ This method requires two steps - first delete in Supabase, then clean up in Verc
|
||||
- Go to the **Storage** tab
|
||||
- Click on the Supabase project (it will show as "uninstalled")
|
||||
|
||||
|
||||
|
||||
- Scroll down and find the **Settings** tab in the sidebar
|
||||
|
||||
|
||||
|
||||
- Click **Delete Database** to completely remove it
|
||||
|
||||
|
||||
|
||||
|
||||
### Method 2: Delete directly from Vercel (removes from both platforms)
|
||||
|
||||
@@ -49,13 +49,13 @@ This method deletes the project from both Vercel and Supabase in one action.
|
||||
|
||||
Find and click the **Settings** tab in the sidebar.
|
||||
|
||||
|
||||
|
||||
|
||||
4. **Delete the project**
|
||||
|
||||
Scroll down and click **Delete Database**. This removes the project from both Vercel and Supabase simultaneously.
|
||||
|
||||
|
||||
|
||||
|
||||
## Transferring projects from Vercel organizations
|
||||
|
||||
@@ -68,7 +68,7 @@ If you want to move a Vercel-linked project to a different organization:
|
||||
|
||||
Go to your [project settings](/dashboard/project/_/settings/general) and look for **"Transfer Project"**. Transfer your project to a different organization.
|
||||
|
||||
|
||||
|
||||
|
||||
Note: The owner must be a member of both the source and target organizations. Transferring a Vercel-managed project will remove its linked Vercel storage from your team.
|
||||
|
||||
@@ -93,13 +93,13 @@ If you want to move a Vercel-linked project to a different organization:
|
||||
|
||||
Go to your [organization settings](/dashboard/org/_/general) and click **"Delete organization in Vercel Marketplace"**. This opens the Vercel settings page.
|
||||
|
||||
|
||||
|
||||
|
||||
2. **Uninstall integration**
|
||||
|
||||
Scroll down and click **Uninstall Integration** to fully remove the organization and disconnect it from Vercel.
|
||||
|
||||
|
||||
|
||||
|
||||
## Important notes
|
||||
|
||||
|
||||
@@ -17,7 +17,7 @@ Knowing which backend your project uses helps you understand where your database
|
||||
|
||||
In the Lovable interface, click the **Cloud icon** on the top bar of your project editor. This section shows which backend your project is currently connected to.
|
||||
|
||||
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> The Cloud icon appears for all projects, regardless of which backend type you're using. Click it to see your actual backend configuration.
|
||||
@@ -28,7 +28,7 @@ Once you open the Cloud settings, you see one of two interfaces depending on you
|
||||
|
||||
If the page shows a menu and screens to manage your Database tables, and Users from within Lovable (similar to the screenshot below), then your backend is managed by **Lovable Cloud**.
|
||||
|
||||
|
||||
|
||||
|
||||
Your Supabase instance in this case is **owned and managed by Lovable**, not by your personal Supabase account.
|
||||
You won’t see this project in your Supabase Dashboard, and you won’t have access to service role keys or direct database URLs.
|
||||
@@ -37,7 +37,7 @@ You won’t see this project in your Supabase Dashboard, and you won’t have ac
|
||||
|
||||
If the page displays the Supabase icon, your Supabase project name, and some links that direct you to the Supabase Dashboard (similar to the screenshot below), then your Lovable project is connected to a **Supabase project you manage directly**.
|
||||
|
||||
|
||||
|
||||
|
||||
## Summary
|
||||
|
||||
|
||||
+1
-5
@@ -105,8 +105,4 @@ If your task is particularly long, you can speed it up by boosting your computin
|
||||
HSNW indexes can produce temporary files during their construction that may consume a few GBs worth of disk.
|
||||
Consider increasing the disk size in the [Infrastructure settings](/dashboard/project/_/settings/infrastructure) to accommodate for short-term disk stress.
|
||||
|
||||
<img
|
||||
width="947"
|
||||
alt="Screenshot 2024-06-10 at 8 00 28 PM"
|
||||
src="https://github.com/supabase/supabase/assets/91111415/9820e214-8796-4b56-91a3-2e73e4836b2f"
|
||||
/>
|
||||
|
||||
+1
-1
@@ -61,6 +61,6 @@ After calling your function, you can check your [edge function logs](/dashboard/
|
||||
|
||||
> Note: search filters are case sensitive and must be present in the event message.
|
||||
|
||||
|
||||
|
||||
|
||||
> Note: excessively long JSON logs may be truncated. If this occurs, use the [JSON.stringify()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON/stringify) function to convert the JSON object into text. You can then copy and paste the log into a [JSON beautifier.](https://jsonformatter.org/)
|
||||
@@ -11,8 +11,8 @@ github_url: 'https://github.com/orgs/supabase/discussions/27022'
|
||||
|
||||
Here are examples of unhealthy CPU utilization:
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
The CPU chart shows 4 distinct metrics of interest:
|
||||
|
||||
|
||||
@@ -44,19 +44,19 @@ There are other metrics that indicate IO strain.
|
||||
|
||||
This example shows a 16XL database exhibiting severe IO strain:
|
||||
|
||||
|
||||
|
||||
|
||||
Its Disk IOPS is constantly near peak capacity:
|
||||
|
||||
|
||||
|
||||
|
||||
Its throughput is also high:
|
||||
|
||||
|
||||
|
||||
|
||||
As a side-effect, its CPU is encumbered by heavy Busy IOWait activity:
|
||||
|
||||
|
||||
|
||||
|
||||
Excessive IO usage is highly problematic as it clarifies that your database is expending more IO than it normally is intended to manage. This can be caused by
|
||||
|
||||
|
||||
@@ -9,8 +9,8 @@ When you create a function and call it from a trigger the NEW variable is only p
|
||||
|
||||
The UI currently defaults to STATEMENT which will not provide NEW or OLD variables to the function.
|
||||
|
||||
|
||||
|
||||
|
||||
Also in SQL (reference: https://www.postgresql.org/docs/current/sql-createtrigger.html)
|
||||
|
||||
|
||||
|
||||
@@ -13,11 +13,11 @@ When executing operations in the Supabase dashboard, there are situations where
|
||||
|
||||
Here is an example of a toast error message:
|
||||
|
||||
|
||||
|
||||
|
||||
Here is an example of a toast success message:
|
||||
|
||||
|
||||
|
||||
|
||||
## What causes it?
|
||||
|
||||
|
||||
@@ -44,11 +44,7 @@ FROM pg_stat_activity where application_name ilike 'pg_cron scheduler';
|
||||
|
||||
If the query does not return a row, the worker has died. To revive it, you must go to the [General Settings](/dashboard/project/_/settings/general) and initiate a fast reboot:
|
||||
|
||||
<img
|
||||
width="719"
|
||||
alt="Screenshot 2024-10-29 at 12 27 24 AM"
|
||||
src="https://github.com/user-attachments/assets/d7a2956c-08e0-4ebc-be08-d14a2383f36b"
|
||||
/>
|
||||
|
||||
|
||||
#### Check the `cron.job_run_details` table for more information
|
||||
|
||||
|
||||
@@ -115,11 +115,7 @@ The below example gives Prisma full authority over all database objects in the p
|
||||
|
||||
In the [Query Performance Advisor](/dashboard/project/_/database/query-performance), you can view long-running or frequently accessed queries by role:
|
||||
|
||||
<img
|
||||
width="1509"
|
||||
alt="Screenshot 2024-06-19 at 1 25 16 PM"
|
||||
src="https://github.com/supabase/supabase/assets/91111415/46e2feae-9fca-4436-a957-2c995eb5ca92"
|
||||
/>
|
||||
|
||||
|
||||
Selecting a query can reveal suggestions to improve its performance
|
||||
|
||||
|
||||
@@ -4,7 +4,7 @@ description: 'Explains what causes unhealthy service indicators in Project Statu
|
||||
topics: ['Troubleshooting', 'Supabase Platform', 'Dashboard']
|
||||
---
|
||||
|
||||
|
||||
|
||||
|
||||
If the project was recently restored, it can take up a couple minutes to become fully operational.
|
||||
|
||||
|
||||
@@ -15,17 +15,13 @@ A 500 error in Auth typically indicates an issue with an external dependency, su
|
||||
|
||||
Ensure you have access to the [SQL Editor](/dashboard/project/_/sql/new?skip=true&source=logs), set the query source to **Logs**, and set the time range appropriately:
|
||||
|
||||
|
||||
|
||||
|
||||
#### Improving log readability
|
||||
|
||||
Logs are displayed in a table format, which can be challenging to read. Double-clicking on a row will expand it for easier viewing:
|
||||
|
||||
<img
|
||||
width="1012"
|
||||
alt="Screenshot 2024-08-14 at 1 15 26 PM"
|
||||
src="https://github.com/user-attachments/assets/6f4c833c-ae15-41e1-9aa8-48ebd58741a1"
|
||||
/>
|
||||
|
||||
|
||||
### Section 1: Checking for database-level errors
|
||||
|
||||
|
||||
+1
-1
@@ -13,7 +13,7 @@ To find your hostname, navigate to the dashboard and click [Connect](/dashboard/
|
||||
|
||||
Example Hostname: `db.zcjtzmeifsoteyjytnbc.supabase.co`
|
||||
|
||||
|
||||
|
||||
|
||||
## Managing your IP address
|
||||
|
||||
|
||||
@@ -8,15 +8,7 @@ Projects paused for more than 1 year can no longer be restored through Supabase
|
||||
|
||||
Both the database backup and Storage objects can be downloaded from the [Project Overview](/dashboard/project/_) section in Supabase Studio before the project is deleted.
|
||||
|
||||
<Image
|
||||
alt="Restore project after pause"
|
||||
src={{
|
||||
dark: '/docs/img/restore-after-90-day-dark.png',
|
||||
light: '/docs/img/restore-after-90-day-light.png',
|
||||
}}
|
||||
width={1600}
|
||||
height={900}
|
||||
/>
|
||||
|
||||
|
||||
Check this [short video walk-through](https://youtu.be/ktsgm8HxWqo?si=5_8IVzL1rp8MWv7m) of the full migration process.
|
||||
|
||||
|
||||
+1
-1
@@ -16,7 +16,7 @@ This is an intermediate and actionable guide for Postgres optimization within th
|
||||
Supabase has an [open-source Grafana Repo](https://github.com/supabase/supabase-grafana) that displays real-time metrics of your database. Although the [Observability Dashboard](/dashboard/project/_/observability) provides similar metrics, it averages the data by the hour or day. Having visibility over how your database responds to changes helps to ensure that the database is not stressed by the index-building process.
|
||||
|
||||
_Visual of Grafana Dashboard_
|
||||
|
||||
|
||||
|
||||
It can be run locally within Docker or can be deployed for free to fly.io. Installation instructions can be found in [Supabase's metrics docs](/docs/guides/observability/metrics/grafana-self-hosted)
|
||||
|
||||
|
||||
@@ -33,11 +33,7 @@ They sit between the database and your client servers. They are solely optimized
|
||||
|
||||
Supabase provides 3 database connection strings that can be used simultaneously if necessary. You can find them on the dashboard by clicking [Connect](/dashboard/project/_?showConnect=true).
|
||||
|
||||
<img
|
||||
width="999"
|
||||
alt="Screenshot 2024-07-04 at 10 40 38 AM"
|
||||
src="https://github.com/supabase/supabase/assets/91111415/1d653203-84d9-406a-a7c9-1f7d097f5a29"
|
||||
/>
|
||||
|
||||
|
||||
### Direct connections:
|
||||
|
||||
@@ -129,11 +125,7 @@ No, it doesn't. See why:
|
||||
|
||||
In the [Dashboard's Database Settings](/dashboard/project/_/database/settings), you can configure Supavisor's "Pool Size":
|
||||
|
||||
<img
|
||||
width="673"
|
||||
alt="Screenshot 2024-02-25 at 10 06 25 PM"
|
||||
src="https://github.com/supabase/supabase/assets/91111415/ce9e9d28-67c2-4dd2-ac0a-0a0150e63b4f"
|
||||
/>
|
||||
|
||||
|
||||
You can also change the pool size for PostgREST's (DB API) internal pooler at the bottom of the [application settings](/dashboard/project/_/settings/api).
|
||||
|
||||
|
||||
@@ -63,7 +63,7 @@ This deploys all functions within the `supabase/functions` to the target project
|
||||
1. In the source project, navigate to **Edge Functions** from the side menu
|
||||
|
||||
2. Using the `Download` button, download your desired function as zip:
|
||||
|
||||
|
||||
|
||||
3. In the target project, navigate to **Edge Functions** from the side menu
|
||||
|
||||
@@ -73,6 +73,6 @@ This deploys all functions within the `supabase/functions` to the target project
|
||||
|
||||
6. Add your function name and click on the `Deploy function` button to deploy the function:
|
||||
|
||||
|
||||
|
||||
|
||||
With this, you can transfer your edge functions between your Supabase projects.
|
||||
@@ -67,7 +67,7 @@ const { data, error } = await supabase
|
||||
|
||||
**Execution Time: 0.069 ms:** measures how long it took to execute the query, including retrieving the data, performing any sorts, joins, or other operations defined in the execution plan, and returning the final results. This time is measured in milliseconds.
|
||||
|
||||
|
||||
|
||||
|
||||
## Detailed components in explain analyze
|
||||
|
||||
@@ -188,7 +188,7 @@ So, the acceptable performance threshold can vary by application. For real-time
|
||||
## Tools to interpret explain analyze output
|
||||
|
||||
Since reading a longer execution plan is quite cumbersome, you can use the website https://explain.depesz.com/ to better visualize the query. If you paste the execution plan in the text area and hit “Submit”, you will get output like this:
|
||||
|
||||
|
||||
|
||||
## Tips for optimizing queries
|
||||
|
||||
|
||||
+1
-1
@@ -9,7 +9,7 @@ github_url: 'https://github.com/orgs/supabase/discussions/27479'
|
||||
|
||||
This discussion explains your organization's usage metrics, which can be found here: [https://supabase.com/dashboard/org/\_/usage](/dashboard/org/_/usage).
|
||||
|
||||
|
||||
|
||||
|
||||
These metrics are calculated based on all the projects under the organization that meet these criteria:
|
||||
|
||||
|
||||
@@ -14,13 +14,13 @@ Hey everyone, i've been hearing feedback about how challenging it can be to get
|
||||
|
||||
## For `smtp-relay.gmail.com`
|
||||
|
||||
|
||||
|
||||
|
||||
(The "Require TLS encryption" option didn't seem to affect anything when tested)
|
||||
(The "Require TLS encryption" option didn't seem to affect anything when tested)
|
||||
|
||||
## For `smtp.gmail.com`
|
||||
|
||||
|
||||
|
||||
|
||||
A lot of this was figured out through trial and error.
|
||||
This is unlikely to be a Supabase Auth bug because Supabase Auth uses the [native Golang SMTP library ](https://pkg.go.dev/net/smtp). If you still have issues setting up Google SMTP, you can try switching to one of these SMTP providers:
|
||||
|
||||
+1
-1
@@ -8,6 +8,6 @@ github_url: 'https://github.com/orgs/supabase/discussions/12946'
|
||||
Why are redirects going to localhost instead of the production site URL?
|
||||
In order for the provided `redirectTo` option to work you must set the exact URL in the shown Redirect URL's setting.
|
||||
|
||||
|
||||
|
||||
|
||||
For more information on formats for redirect URL settings see the documentation here: https://supabase.com/docs/guides/auth/redirect-urls#use-wildcards-in-redirect-urls
|
||||
+1
-5
@@ -7,11 +7,7 @@ github_url: 'https://github.com/orgs/supabase/discussions/21579'
|
||||
|
||||
The dashboard makes requests to the health endpoints of the Supabase services (Database, Auth, Data API, Realtime, Edge Functions to ensure everything is working). These requests appear in the charts about your project:
|
||||
|
||||
<img
|
||||
width="1135"
|
||||
alt="image"
|
||||
src="https://github.com/supabase/supabase/assets/5036432/08b1c142-289c-46f3-ac21-38faad50ef8a"
|
||||
/>
|
||||
|
||||
|
||||
You can see these requests to the health endpoints from the log explorer here:
|
||||
|
||||
|
||||
Reference in new issue
Block a user