-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
docs(self-hosted): Restructure experimental section into 'Production Enhancements' and 'Optional Features' #15376
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
docs(self-hosted): Restructure experimental section into 'Production Enhancements' and 'Optional Features' #15376
Conversation
…Enhancements' and 'Optional Features' These pages were never experimental, most of them are battle tested and enhances the operational side of self-hosted. Marking it as experimental confuses newcomers.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
Turns out I need to add |
…/restructure-experimental-section
…f github.com:getsentry/sentry-docs into aldy505/self-hosted/restructure-experimental-section
BYK
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.
Love it!
| These are community-contributed docs. Sentry does not officially provide support for self-hosted configurations beyond the default install. | ||
| </Alert> | ||
|
|
||
| In some cases, storing Sentry data on-disk is not really something people can do. Sometimes, it's better to offload it into some bucket storage (like AWS S3 or Google Cloud Storage). |
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 mentioning the new Seaweed system and the default S3 enabled backend is important here.
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.
But.... we'll have objectstore soon.
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.
Not so soon. Even then, useing seaweed for all things storage on self-hosted would be good.
| ### Uptime Checker | ||
| You can configure Uptime Checker to send metrics to Statsd server by configuring your `docker-compose.yml` file: |
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.
They should be using the override file instead of the main one, right?
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.
Or lets add these to env to pass on the already existing env variables for these and people can set them in their .env files
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.
yeah it should be override
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'd actually go with the second option: add these to pass in already set env variables and just document these.
|
ugh why did I leave it on auto merge... |
DESCRIBE YOUR PR
These pages were never experimental, most of them are battle tested and enhances the operational side of self-hosted. Marking it as experimental confuses newcomers.
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: