Repository navigation
labs/vector-route-dual-write: Vector route to ClickStack next to Loki - #162
Merged
Merged
Conversation
…, sink buffer modes under a ClickHouse outage Closes #161 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
New lab, run end to end on local k3d on 2026-11-13 (Vector 0.61.0, clickstack-all-in-one 2.44.0 / ClickHouse 26.8.36.3, Loki 3.7.9, Kong 3.9.4).
routetransform sends two Kong gateways and one API deployment intologs.kong_access/logs.app_logs. Counts match Loki exactly (300/300/600); unmatched pods reach Loki only.block(default) stalls the whole source, Loki included, then delivers everything;drop_newestkeeps Loki whole and drops exactly the counted rows; a 256 MiB disk buffer keeps both.UInt32column failed a 1,000-row insert with HTTP 400 and Vector dropped the batch (not retriable); latency columns areInt32now.lab.yamlhas no publishing keys (card left to the owner).Not covered: GCP Private Service Connect, Cloud regions, a dedicated insert-only user, log rotation during long outages.
Closes #161
🤖 Generated with Claude Code