ST consumer config structure #107456
Closed
ST consumer config structure #107456
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Create detailed documentation mapping 'I need to change X' → 'edit file Y' - Document file structure for ST consumer config in ops repo - Include quick reference table for common configuration tasks - Add examples for KEDA autoscaling, Kafka topics, and regional overrides - Document configuration hierarchy and precedence - Provide debugging tips and common workflows Resolves INC-1567: Document ops repo structure for ST consumer config Co-authored-by: shashank.jarmale <shashank.jarmale@sentry.io>
Contributor
|
Cursor Agent can help with this pull request. Just |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds comprehensive documentation for the ST consumer configuration structure to address the issue of scattered configuration files.
This PR introduces
docs/ST_CONSUMER_CONFIGURATION.md, which includes:This documentation aims to improve clarity and reduce the effort required for engineers to locate and modify ST consumer configurations.
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.
Linear Issue: ID-1303