docs: fix sentry-logs dev stack comment to reference consumoor instead of vector#838
Open
detail-app[bot] wants to merge 1 commit into
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Development section of docs/sentry-logs.md listed
vectoras one of the services started bymake sentry-logs-dev, but the Vector HTTP-Kafka pipeline was replaced byxatu-consumoorand the Makefile target now startsxatu-consumoorinstead.Introduced by commit 908ea1c (@samcm, #834)
A developer setting up the sentry-logs dev stack would read the comment, expect a Vector container to be running, and waste time looking for
xatu-vector-http-kafkalogs when debugging why events are not reaching ClickHouse — when in fact the relevant service isxatu-consumoor.Doc Drift PRs can be configured here.