-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
feat(partners)add-enablement-docs #14095
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
base: master
Are you sure you want to change the base?
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
|
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 |
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 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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
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.
we can link to : https://docs.sentry.io/platforms/
|
||
- **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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add some who are doing this already?
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.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mentioned above already, maybe we should just link to all: https://docs.sentry.io/api/permissions/
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