Skip to content

Vulture: check recent traces#5157

Merged
ruslan-mikhailov merged 6 commits intografana:mainfrom
ruslan-mikhailov:vulture-recent-blocks
May 28, 2025
Merged

Vulture: check recent traces#5157
ruslan-mikhailov merged 6 commits intografana:mainfrom
ruslan-mikhailov:vulture-recent-blocks

Conversation

@ruslan-mikhailov
Copy link
Copy Markdown
Contributor

@ruslan-mikhailov ruslan-mikhailov commented May 23, 2025

What this PR does:

  1. Refactoring to simplify code and reduce copy-paste
  2. For reads, do two checks: for recent traces that are <5 minutes old, and for older traces. This allows to check read path that hits to generators and ingesters.

Which issue(s) this PR fixes:
Fixes #

How it has been tested:

  1. unit tests
  2. run the new version in k8s for 4h+. Results: no errors reported

Additionally, checked via debug logs that checks run correctly

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

Comment thread cmd/tempo-vulture/main.go Outdated
@ruslan-mikhailov ruslan-mikhailov force-pushed the vulture-recent-blocks branch from 54fcc94 to 6604866 Compare May 27, 2025 12:25
@ruslan-mikhailov
Copy link
Copy Markdown
Contributor Author

ruslan-mikhailov commented May 27, 2025

+ review fix: increase default value for tempo-recent-traces-backoff-duration

@ruslan-mikhailov ruslan-mikhailov requested a review from mapno May 27, 2025 12:26
Copy link
Copy Markdown
Contributor

@mapno mapno left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ruslan-mikhailov ruslan-mikhailov merged commit df1abc5 into grafana:main May 28, 2025
19 checks passed
@ruslan-mikhailov ruslan-mikhailov deleted the vulture-recent-blocks branch May 28, 2025 09:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants