Files
supabase/apps/studio/components/interfaces/Reports/ReportBlock/UnavailableChartBlock.tsx
T
Lukas Bernert d51ed9f451 Update Studio disk IO burst copy (#50809)
## Problem

Studio copy ties disk IO burst behavior to compute size thresholds and
says the IO budget "resets".
Burst eligibility isn't a single size cutoff
EBS burst credits refill continuously while disk usage runs below
baseline

Docs already use this framing (#50016)

Fixes PROD-665

## Solution

Three copy changes:

- `UnavailableChartBlock.tsx`: the burst balance chart placeholder no
longer names a size. It now describes sustained IO with no burst credit
pool
- `database-charts.ts`: the Disk IO Burst Balance tooltip describes the
EBS burst credit pool without referencing instance size
- `ResourceExhaustionWarningBanner.constants.ts`: the warning and
critical banners say the budget refills whenever disk usage runs below
baseline, instead of "resets"

## Review instructions

1. Read the diff. Copy changes only.
2. Optional: on a project with burstable disk IO, open Reports >
Database and hover the Disk IO Burst Balance chart title to see the new
tooltip.

## Checklist

Check all before review:

- [x] I have read
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
- [x] If I wrote a new docs topic or edited an existing topic, I used
the `/write-the-docs` or `/edit-the-docs` skill, which references
[WORD_LIST](https://github.com/supabase/supabase/blob/master/apps/docs/WORD_LIST.md)
and the docs
[CONTRIBUTING](https://github.com/supabase/supabase/blob/master/apps/docs/CONTRIBUTING.md)
guide

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

## Documentation

* Updated disk I/O chart messaging to explain that some compute types
sustain disk throughput without a burst credit pool to track.
* Clarified that disk I/O burst budgets refill when demand is at or
below baseline, and that throughput remains at baseline until the budget
refills.
* Updated the burst-balance chart tooltip to describe how compute uses
the EBS burst credit pool.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-09-23 22:44:23 +02:00

33 lines
1.0 KiB
TypeScript

import { ReactNode } from 'react'
import { ReportBlockContainer } from './ReportBlockContainer'
import { InstanceHealthIcon } from '@/lib/constants/metrics'
interface UnavailableChartBlockProps {
label: string
actions?: ReactNode
}
export const UnavailableChartBlock = ({ label, actions }: UnavailableChartBlockProps) => {
return (
<ReportBlockContainer
draggable
showDragHandle
loading={false}
icon={<InstanceHealthIcon size={14} className="text-foreground-muted" />}
label={label}
actions={actions}
>
<div className="flex flex-1 flex-col justify-center gap-y-1 px-5 py-4">
<p className="text-xs text-foreground-light">
This chart isn't available on your current compute size
</p>
<p className="text-xs text-foreground-lighter">
Your compute's disk IO runs at a sustained rate. There's no burst credit pool to track.
You can remove this chart from your report.
</p>
</div>
</ReportBlockContainer>
)
}