Skip to content
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

feat(devserver): Run separate transactions post process forwarder #40130

Merged
merged 2 commits into from
Oct 17, 2022

Conversation

lynnagara
Copy link
Member

@lynnagara lynnagara commented Oct 17, 2022

Combined post process forwarder no longer works with Sentry/Snuba defaults (fully separated errors/transactions topics).

Running a combined PPF caused this error in self hosted: #40120.

In the future it may be nice to support a PPF implementation that can consume from multiple topics in order to reduce the amount of docker containers in dev / low volume environments but this is not currently possible.

Combined post process forwarder no longer works with Sentry/Snuba
defaults (fully separated errors/transactions topics).

Running a combined PPF caused this error in self hosted: #40120.
"--loglevel=debug",
"--commit-batch-size=100",
"--commit-batch-timeout-ms=1000",
],
"post-process-forwarder-transactions": [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to include this down below where we do the following:

if eventstream.requires_post_process_forwarder():
    daemons += [_get_daemon("post-process-forwarder")]

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, added

@lynnagara lynnagara merged commit cf472c7 into master Oct 17, 2022
@lynnagara lynnagara deleted the update-devserver branch October 17, 2022 22:59
barkbarkimashark pushed a commit that referenced this pull request Oct 18, 2022
…0130)

Combined post process forwarder no longer works with Sentry/Snuba
defaults (fully separated errors/transactions topics).

Running a combined PPF caused this error in self hosted:
#40120.

In the future it may be nice to support a PPF implementation that can
consume from multiple topics in order to reduce the amount of docker
containers in dev / low volume environments but this is not currently
possible.
@github-actions github-actions bot locked and limited conversation to collaborators Nov 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants