Skip to content

docs(self-hosted): update data flow diagram#18454

Open
aldy505 wants to merge 1 commit into
masterfrom
aldy505/self-hosted/update-data-flow-diagram
Open

docs(self-hosted): update data flow diagram#18454
aldy505 wants to merge 1 commit into
masterfrom
aldy505/self-hosted/update-data-flow-diagram

Conversation

@aldy505

@aldy505 aldy505 commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

DESCRIBE YOUR PR

Tell us what you're changing and why. If your PR resolves an issue, please link it so it closes automatically.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

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.

EXTRA RESOURCES

@vercel

vercel Bot commented Jun 17, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
develop-docs Ready Ready Preview, Comment Jun 17, 2026 1:41am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
sentry-docs Ignored Ignored Preview Jun 17, 2026 1:41am

Request Review

@aldy505 aldy505 requested a review from BYK June 17, 2026 01:35
kafka -- Fetch tasks --> taskbroker
taskbroker -- Process and analyze mobile app --> launchpad
taskworker -- Fetch tasks to execute --> taskbroker
taskworker -- As a buffer and distributed lock --> redis

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Bug: The data flow diagram incorrectly shows a taskworker to redis connection and places task components in the wrong subgraph.
Severity: LOW

Suggested Fix

Update the Mermaid diagram in develop-docs/self-hosted/data-flow.mdx. Remove the connection between taskworker and redis. Move the taskbroker and taskworker nodes from the 'Event Processing' subgraph to the 'Web User Interface' subgraph to align with the textual description and the current architecture.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: develop-docs/self-hosted/data-flow.mdx#L49

Potential issue: The data flow diagram in `develop-docs/self-hosted/data-flow.mdx`
contains inaccuracies regarding the task processing architecture. It incorrectly shows a
connection from `taskworker` to `redis`, which is a remnant of a deprecated
architecture; `taskworker` now communicates with `taskbroker` via gRPC. Additionally,
the diagram places `taskbroker` and `taskworker` within the 'Event Processing' subgraph,
which contradicts the textual description in the same file that associates them with the
'Web User Interface' flow.

Also affects:

  • develop-docs/self-hosted/data-flow.mdx:46~56

Did we get this right? 👍 / 👎 to inform future reviews.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant