Add --max-start-time and --min-start-time flags to tempo-cli analyse blocks command
#3250
Conversation
This file contains 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
mapno
requested review from
jdbaldry,
knylander-grafana,
joe-elliott,
annanay25,
mdisibio,
kvrhdn,
zalegrala,
electron0zero,
ie-pham and
stoewer
as code owners
joe-elliott
reviewed
Jan 2, 2024
mapno
force-pushed
the
analyse-blocks-max-start-time
branch
from
fdaeac6
to
beac967
Compare
joe-elliott
approved these changes
Feb 9, 2024
kvrhdn
pushed a commit
to kvrhdn/tempo
that referenced
this pull request
Feb 26, 2024
…lyse blocks` command (grafana#3250) * Add flag to tempo-cli command * Docs * Add min time as well * Fix chlog * Fix condition
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.
What this PR does:
Add
--max-start-timeand--min-start-timeflags to tempo-clianalyse blockscommand. With these parameters the analysis can be limited to a given time range.Checklist
CHANGELOG.mdupdated - the order of entries should be[CHANGE],[FEATURE],[ENHANCEMENT],[BUGFIX]