Skip to content

Conversation

@aldy505
Copy link
Collaborator

@aldy505 aldy505 commented Dec 7, 2025

DESCRIBE YOUR PR

Avoid confusion around reseting Kafka offsets for folks that don't really touch Kafka in their life.

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

EXTRA RESOURCES

@vercel
Copy link

vercel bot commented Dec 7, 2025

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

Project Deployment Preview Comments Updated (UTC)
develop-docs Ready Ready Preview Comment Dec 7, 2025 4:22am
1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
sentry-docs Ignored Ignored Preview Dec 7, 2025 4:22am

@aldy505 aldy505 changed the title k docs(self-hosted): more refined instructions for proper solution of kafka offset out of range error Dec 7, 2025
@aldy505 aldy505 requested a review from Copilot December 7, 2025 01:25
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR improves the documentation for resolving Kafka offset out of range errors in self-hosted Sentry installations by providing more detailed, step-by-step instructions and clarifying the "proper solution" approach.

Key Changes

  • Enhanced step-by-step instructions with concrete examples showing how to identify consumer groups from docker-compose.yml
  • Added clarification that multiple containers may share the same consumer group and all must be stopped
  • Improved explanations for data loss implications in the nuclear option

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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.

2 participants