Conversation
Draft of converting 2 internal docs into public facing partnership enablement pages - account provisioning - oauth
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
|
do we want something on the landing page? 
|
Bundle ReportChanges will increase total bundle size by 600 bytes (0.0%) ⬆️. This is within the configured threshold ✅ Detailed changes
ℹ️ *Bundle size includes cached data from a previous commit Affected Assets, Files, and Routes:view changes for bundle: sentry-docs-server-cjsAssets Changed:
view changes for bundle: sentry-docs-client-array-pushAssets Changed:
|
|
@brianthi it would be valuable to consider us making a billing page as well, similar to these |
sentaur-athena
left a comment
sentaur-athena
left a comment
There was a problem hiding this comment.
I think this is a great start and even whithout billing info having it is better than not.
|
|
||
| ## Overview | ||
|
|
||
| When you call the Sentry provisioning API on behalf of your customer for the first time, the customer receives: |
There was a problem hiding this comment.
The customer would need all but integration token is basically only useful for the partner.
|
|
||
| ### Supported Platforms | ||
|
|
||
| The `platform` field supports all Sentry platform identifiers, including: |
|
|
||
| - **Partner Presence**: Show your platform as an organization member | ||
| - **Persistent Plan**: Allow customers to upgrade plans independently | ||
| - **Quota Visibility**: Control visibility of usage quotas |
There was a problem hiding this comment.
Billing is always the biggest question, I think high level at this point we can add we have the option for them to sponsor their customers.
| 4. **Respect rate limits**: Implement appropriate delays between requests | ||
| 5. **Secure your secret key**: Store your API_SECRET_KEY securely and never expose it in client-side code | ||
|
|
||
| ## Support |
There was a problem hiding this comment.
I wonder if we should take a more marketing approach here. Like get people excited to reach out or just leave it as a reference.
|
|
||
| # Partnership Platform | ||
|
|
||
| Sentry offers powerful partnership capabilities that allow you to integrate error monitoring and performance insights directly into your platform. Whether you're a developer platform, hosting provider, or SaaS application, you can leverage Sentry's monitoring capabilities to enhance your customer experience. |
There was a problem hiding this comment.
Can we add some who are doing this already?
There was a problem hiding this comment.
specific partner examples? That get's into a topic of we just have to check with legal which logos we are allowed to mention in such a doc
we could address a lot of content topics, and merge, then figure that out later, for a smaller addition to the doc then
| - **Home Page URL**: Your platform's homepage | ||
| - **Privacy Policy URL**: Your privacy policy | ||
| - **Terms and Conditions URL**: Your terms of service | ||
| - **Required Scopes**: APIs your platform needs to access |
There was a problem hiding this comment.
You can link to https://docs.sentry.io/api/permissions/ for list of scopes
|
|
||
| ## API Scopes | ||
|
|
||
| Scopes define what permissions your application has. Common scopes include: |
There was a problem hiding this comment.
mentioned above already, maybe we should just link to all: https://docs.sentry.io/api/permissions/
* 'master' of https://github.com/getsentry/sentry-docs: (22 commits) Fix incorrectly placed comma (#14592) fix(devservices): Typo in devservices docs (#14636) ref(ourlogs): Add log size limit (#14635) Document undocumented php prefix option (#14634) getsentry/relay@7958273 Unreal Engine: Update plugin docs (#14624) feat: Update min js sdk version for logging and update console logging snippet (#14614) feat: [Unreal] Add transaction and span set_data documentation (#14599) feat(js): Add `ignoreSpans` documentation to Options page (#14572) fix(js/browser): Amend user IP + `sendDefaultPii` change to v10 migration guide (#14609) fix: Fix broken AI banner due to invalid syntax (#14627) feat(partners)add-enablement-docs (#14095) Fix image path issue & add test coverage for new lightbox (#14616) feat(seer): update GHE setup to work with seer (#14617) fix(replay): Document searchable properties `screen` and alias `screens` (#14603) Update image handling (#14564) Update using-hooks.mdx (#14605) Godot: Document `disabled-in-editor-play` option (#14438) fix(Docs) redirect and deprecate old metrics pages (#14602) fix(relay): Update projects.mdx (#14606) ...
2 participants
Draft of converting 2 internal docs into public facing partnership enablement pages
New section under "product walkthroughs" which "walkthrough" is maybe a stretch, but this is a start and we can put it where we agree makes the most sense, and be discoverable.
preview