[sentry-junior]

sentry devserver loaded all of Sentry (~7–10 s) only to read settings, pick its daemons, and create Kafka topics. Then the web server started and loaded all of Sentry again. On a fresh boot, Kafka usually answers only at about that moment, so the web also waited for Kafka.

Now the devserver:

• Loads settings only, through a new settings_configuration decorator (configure(settings_only=True)). The paths that serve from this process (--debug-server, and no daemons) still run the full configure().
• Decides on the post-process forwarder from SENTRY_EVENTSTREAM, because asking the backend imports models. A test checks the list against every EventStream subclass's requires_post_process_forwarder().
• Creates Kafka topics in a background thread, so the web starts right away. The thread probes Kafka with a fresh client until Kafka answers. A client that can't reach Kafka backs off for up to 10 s, which cost ~9 s when settings loaded before Kafka was up.
• Holds back the consumers until the topics exist. A consumer that subscribes to a missing topic crashes with UNKNOWN_TOPIC_OR_PART, and that stops everything. honcho runs commands through sh, so each consumer command first waits for .artifacts/devserver-kafka-topics-ready.
• Prints the traceback and stops the whole devserver if creating topics fails.
• Lets child processes validate the backends. Before, the parent validated them and then set SENTRY_SKIP_BACKEND_VALIDATION for its children.

Time from launch to the first 200 on /auth/login/ through rsbuild on :8000, measured in a sandbox with devservices up (3 starts each):

• Kafka already up: 12.7 / 13.5 / 13.3 s before, 9.3 / 8.4 / 8.8 s after.
• Kafka container just started: 18.6 / 19.2 / 18.2 s before, 8.3 / 10.5 / 9.7 s after.

With every topic deleted and --workers --occurrence-ingest, the web answered in 10.3 s. All topics existed 19 s after launch, and only then did the consumer start and get its partitions. A bad cluster mapping printed its KeyError traceback to the terminal and dev.log, then stopped every process.

via Ming Chen.

--

View Session [Sentry]

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit b0728dc. Configure here.}