feat(spans): Add flusher log support to GCP log analyzer tool#109080
Draft
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>
github-actions
bot
added
the
Scope: Backend
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
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
1 participant
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) in addition to the existingbuffer logger support (
spans.buffer.slow_evalsha_operations).This enables analyzing which traces are flushing the most bytes, spans, and
segments across flusher processes, helping identify traces that are most
impactful on span buffer resources.
New capabilities:
--log-type flusherflag to analyze flusher logs (default remainsbuffer)--podflag for filtering by specific k8s pod name (e.g.getsentry-consumer-process-spans-production-6cbd74fb55-cqpvc)New types:
FlusherLogAnalyzer— aggregates flusher log entries by trace, with project/trace filteringFlusherTraceStats,FlusherSummaryStats— data models for flusher analysisFlusherTraceData,FlusherLogEntry— parsed flusher log entry typesExample usage: