-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Add updates to AM2 billing docs #13276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
Bundle ReportChanges will decrease total bundle size by 15 bytes (-0.0%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
|
I cannot find the preview of this page. I went searching, and I found this page (https://docs.sentry.io/pricing/legacy-pricing/), but when I try to access it here (https://sentry-docs-git-am2-pricing.sentry.dev/legacy-pricing/), I get a |
| - **[On-demand volume:](#on-demand-capacity)** An overage budget that kicks in only if your prepaid volume has been used up. Having this makes it possible to control the maximum amount you will spend for overages each month. | ||
|
|
||
| If you run out of **both** your prepaid and on-demand volume, any new data you send will be rejected and you won't be charged for it. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Line 26 on-demand volume link doesn't seem to be attached to an anchor down the page anymore
docs/pricing/legacy-pricing.mdx
Outdated
| ### Per-Category Pricing | ||
|
|
||
| If you'd like to buy either prepaid or on-demand data on top of what's included in your plan, you can buy as much as you think you'll need per data category. [Errors](#errors-pricing), [Performance](#performance-pricing), [Replays](#replays-pricing), [Cron Monitors](#cron-monitors-pricing), [Uptime Monitors](#uptime-monitors-pricing), and [Attachments](#attachments-pricing) each have their own unique pricing structures, as listed in the tables below: | ||
| If you'd like to buy either prepaid or on-demand data on top of what's included in your plan, you can buy as much as you think you'll need per data category. [Errors](#errors-pricing), [Performance and Profiling](#performance-pricing), [Replays](#replays-pricing), [Cron Monitors](#cron-monitors-pricing), [Uptime Monitors](#uptime-monitors-pricing), and [Attachments](#attachments-pricing) each have their own unique pricing structures, as listed in the tables below: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Performance and Profiling <-- this anchor seems to be broken
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! I went ahead and fixed that.
docs/pricing/legacy-pricing.mdx
Outdated
| Depending on how you've configured profiling in your SDK, you will either be sending Transactions with Profiling and be billed using Performance Units as described above, or you will be using Continuous Profiling or UI Profiling and be billed using Profile Hours. | ||
|
|
||
| <Alert> | ||
| To understand more about profiling configuration and migration from Transactions with Profiling to Continuous or UI Profiling, please see this [FAQ.](/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This FAQ link is currently linking to the docs home page.
sfanahata
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are a few broken links that should be updated before this is merged. Otherwise, just a nit, but I can't tell if it's helpful to add that things "can't be purchased in advance", or if it's simple enough to say this is how you purchase these things. I can see an argument for both.
Co-authored-by: Shannon Anahata <[email protected]>
* Add updates to AM2 billing docs * Update docs/pricing/legacy-pricing.mdx Co-authored-by: Shannon Anahata <[email protected]> * Resolve broken anchor links * Prettier format --------- Co-authored-by: Alex Krawiec <[email protected]> Co-authored-by: Shannon Anahata <[email protected]>
DESCRIBE YOUR PR
Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes:
LEGAL BOILERPLATE
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
EXTRA RESOURCES