-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Update AM3 and legacy billing for logs GA, DO NOT MERGE BEFORE LOGS GA #14589
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 GitHub.
1 Skipped Deployment
|
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.
I have a big question about the use of the term "on-demand" in this doc. I know it's a legacy doc, so perhaps it's still the correct term, but when we link to the "explainer" on the term, we link to PAYG. We should either change the terminology to PAYG, or should add the definition of "on-demand" to this doc.
This s a good point @sfanahata, I'll update the doc to make it explicit that on-demand has been rebranded as PAYG. |
Bundle ReportChanges will decrease total bundle size by 60.67kB (-0.27%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-client-array-pushAssets Changed:
view changes for bundle: sentry-docs-server-cjsAssets Changed:
|
But it should stay as on-demand for legacy docs, assuming legacy docs are for customers who are on AM1 and AM2, since we still reference it as "on-demand" for those customers |
@@ -136,6 +144,31 @@ Monitors for Uptime can't be purchased in advance. Uptime monitors are available | |||
|
|||
{/* <!-- prettier-ignore-end --> */} | |||
|
|||
#### Seer Pricing | |||
|
|||
[Seer](/product/ai-in-sentry/seer/) is Sentry's AI agent that triages, debugs, and fixes application issues automatically. Access Seer by adding it to your existing subscription for an additional $20 per month. This $20 gives you $25 worth of Seer event credits, which can be used for any combination of [Issue Scans](/pricing/#issue-scans) or [Issue Fixes](/pricing/#issue-fixes) (see pricing tables below). Any usage beyond this $25 credit will draw from your [on-demand budget](/pricing/#terminology). |
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.
on-demand
budget links to PAYG without context right here. You do now say on-demand is now known as PAYG higher up, so maybe this is fine?
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.
Looks good! A couple of nits/suggestions for your consideration.
Co-authored-by: Shannon Anahata <[email protected]>
Co-authored-by: Brian Thi <[email protected]>
Co-authored-by: Brian Thi <[email protected]>
Co-authored-by: Shannon Anahata <[email protected]>
e50d139
to
acaeb03
Compare
…om/getsentry/sentry-docs into feat/python-docs-improvement-clean * 'feat/python-docs-improvement-clean' of https://github.com/getsentry/sentry-docs: docs(replay): Bring replay nav item to all apple platforms (#14710) User Feedback Basics Page (#14670) Update AM3 and legacy billing for logs GA, DO NOT MERGE BEFORE LOGS GA (#14589) Add LLMSteering component for hidden documentation instructions (#14744) New data retention policy page (#14661) Adding error prediction to Prevent AI docs (#14641)
…om/getsentry/sentry-docs into feat/nextjs-centralized-flow-clean * 'feat/nextjs-centralized-flow-clean' of https://github.com/getsentry/sentry-docs: Fix reference to span in processOrderBatch function (#14741) chore(java): Add docs on how to use tracePropagationTargets (#14752) docs(replay): Bring replay nav item to all apple platforms (#14710) User Feedback Basics Page (#14670) Update AM3 and legacy billing for logs GA, DO NOT MERGE BEFORE LOGS GA (#14589) Add LLMSteering component for hidden documentation instructions (#14744) New data retention policy page (#14661) Adding error prediction to Prevent AI docs (#14641)
* 'master' of https://github.com/getsentry/sentry-docs: (72 commits) docs(replay): Bring replay nav item to all apple platforms (#14710) User Feedback Basics Page (#14670) Update AM3 and legacy billing for logs GA, DO NOT MERGE BEFORE LOGS GA (#14589) Add LLMSteering component for hidden documentation instructions (#14744) New data retention policy page (#14661) Adding error prediction to Prevent AI docs (#14641) feat(logs): Remove beta note from logs docs (#14686) First pass at logs quota doc (#14671) docs(aws): Remove manual setup steps for ESM (#14738) Android Logs docs without Errors / Breadcrumbs distractions (#14733) chore(Unity): Dropped 2019 relevant section from Known Limitations (#14735) feat: Added Unity `UserFeedback` Prefab (#14667) chore(Unity): Added Mono & Line Numbers to Known Limitations (#14736) docs(js): Fix Next.js client tracing config (#14734) chore: Updated known limitation in Unity with Cysharp (#14666) feat(Unity ): Added `APK+OBB` initialization to troubleshooting (#14668) Codecov copy & screenshot edits (#14659) fix(cloudflare): Remove unused instrument.mjs from hono on cloudflare (#14723) update advanced scrubbing doc - adding logs section (#14696) fixing some errors from nextjs-source-map-updates branch (#14467) ...
DESCRIBE YOUR PR
DO NOT MERGE BEFORE LOGS GA.
See changes on:
https://sentry-docs-git-logs-ga-billing.sentry.dev/pricing/
https://sentry-docs-git-logs-ga-billing.sentry.dev/pricing/legacy-pricing/
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