feat(billing): Update spend notifications documentation #10076
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Bundle ReportChanges will increase total bundle size by 15.6kB ⬆️
|
| @@ -8,7 +8,7 @@ Sentry sends you notifications regarding workflow activities, [release deploys]( | |||
|
|
|||
| - [Workflow](#workflow-notifications): Activity involving user actions and state changes on issues. This includes activities such as issue resolution, assignment, comments, and regressions. | |||
| - [Deploy](#deploy-notifications): When a release you have commits on is deployed. | |||
| - [Quota](#quota-notifications): Approaching quotas, exceeded quotas, and spike protection. | |||
| - [Spend](#spend-notifications): Reserved volume warning, depleted quotas, and on-demand capacity usage notifications. | |||
There was a problem hiding this comment.
Can you confirm the copy? There seems to be a shift towards "pre-paid" instead of "reserved" and "pay as you go" instead of "on-demamd".
Otherwise, LGTM.
There was a problem hiding this comment.
"Reserved" is fine, and is a concept we want to keep the same in AM2 and AM3. We're not planning on changing that to "Pre-paid".
"On-Demand" is how AM2 customers see things. However for AM3 orgs, we should change this to "Pay As You Go". Since docs should reflect the latest plan (whereas in-app we show based on their plan), this should be updated from "On-Demand" to "Pay As You Go"
There was a problem hiding this comment.
Sounds good. Does the copy still need to be changed here?
This pull request updates the current docs for the Spend Notifications ready to be released for AM1 and AM2 organizations.
There was a problem hiding this comment.
This copy looks good as is. We will revisit "PAYG" changes with Docs team prior to AM3 launch.
Update "Learn More" link that will point to updated documentation in getsentry/sentry-docs#10076. --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>
dashed
force-pushed
the
spend-notifications/update-docs
branch
from
52b9c63
to
7ef3191
Compare
dashed
force-pushed
the
spend-notifications/update-docs
branch
from
7ef3191
to
ff5b469
Compare
Co-authored-by: Liza Mock <[email protected]>
Co-authored-by: Liza Mock <[email protected]>
Co-authored-by: Liza Mock <[email protected]>
dashed
force-pushed
the
spend-notifications/update-docs
branch
from
ff5b469
to
f489a2a
Compare
Prepare and update documentation in anticipation of the spend notifications feature rollout.