ref(compose): Separate ingest consumers #2193
Merged
Conversation
This file contains 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
|
Anyway we can keep the |
|
See getsentry/snuba#1670 for context (and all the tickets referencing that one) |
|
👍 thanks for the pointer @BYK! I'm aware that the team is currently looking into standardizing the consumer CLI options, which would make it easier to also add a single consumers command that then spawns all of them in default configuration. |
ashwoods
approved these changes
Jun 7, 2023
untitaker
approved these changes
Jun 7, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Ingest consumers will stop to support the
--all-consumer-typesoption, andinstead will need to run separate instances for events, attachments, and
transactions.
See getsentry/sentry#49957