vector: ship logs to clickhouse logs-ingest instead of loki#168
Open
samcm wants to merge 2 commits into
Open
Conversation
Replaces the loki sink in the vector template config with a remap transform + http sink that posts to platform's logs-external clickhouse pipeline at logs-ingest.analytics.production.platform.ethpandaops.io. Reuses secret_loki credentials since the same VMAuth backend fronts both ingresses. New devnets generated from this template will ship logs straight to clickhouse. This mirrors the rollout already done in glamsterdam-devnet-3 (all hosts) and bal-devnet-6 (bootnode-1) where it has been verified end-to-end.
mattevans
approved these changes
May 12, 2026
samcm
commented
May 12, 2026
barnabasbusa
approved these changes
May 12, 2026
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.
Summary
logs-ingest.analytics.production.platform.ethpandaops.io(clickhouse logs-external pipeline).secret_lokicredentials — the same VMAuth backend fronts both ingresses, so no new secret plumbing is needed.