feat(spans): Add flusher log support to GCP log analyzer tool#109080
Merged
feat(spans): Add flusher log support to GCP log analyzer tool#109080
Conversation
Extend the GCP log analyzer to parse and display flusher logger output (spans.buffer.top_flush_operations_by_bytes) in addition to the existing buffer logger support. This enables analyzing which traces are flushing the most bytes, spans, and segments. Changes: - Add FlusherLogAnalyzer, FlusherTraceStats, FlusherSummaryStats - Add FlusherTraceData, FlusherLogEntry, parse_top_flush_operations - Add --log-type flag (buffer/flusher) to CLI - Add --pod flag for filtering by specific k8s pod name - Surface per-phase latency breakdown (load_ids, load_data, decompress) in flusher summary output Co-Authored-By: Claude <noreply@anthropic.com>
evanh
approved these changes
Mar 5, 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.
Extend the GCP log analyzer to parse and display flusher logger output
(
spans.buffer.top_flush_operations_by_bytes) with--log-type flusherflag.
This enables analyzing which traces are flushing the most bytes, shows the
number of spans flushed, and number of segments flushed, helping identify
traces that are most impactful on span buffer resources.
Also adds:
--podflag for filtering by specific k8s pod name (e.g.getsentry-consumer-process-spans-production-abc123defg-abcde)Example usage: