Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue 356 maximum lookback should be retention period #384

Conversation

everett980
Copy link
Collaborator

@everett980 everett980 commented May 21, 2019

Which problem is this PR solving?

Short description of the changes

  • Adds the ability to configure the lookback dropdown on the search page through get-config.tsx

Signed-off-by: Everett Ross <reverett@uber.com>
Signed-off-by: Everett Ross <reverett@uber.com>
@everett980 everett980 requested a review from tiffon May 21, 2019 15:54
@codecov
Copy link

codecov bot commented May 21, 2019

Codecov Report

Merging #384 into master will increase coverage by 0.1%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master     #384     +/-   ##
=========================================
+ Coverage   88.95%   89.06%   +0.1%     
=========================================
  Files         162      162             
  Lines        3640     3658     +18     
  Branches      829      831      +2     
=========================================
+ Hits         3238     3258     +20     
+ Misses        366      364      -2     
  Partials       36       36
Impacted Files Coverage Δ
...ackages/jaeger-ui/src/constants/default-config.tsx 100% <ø> (ø) ⬆️
...er-ui/src/components/SearchTracePage/SearchForm.js 89.07% <100%> (+1.94%) ⬆️
...eViewer/TimelineHeaderRow/TimelineViewingLayer.tsx 91.52% <0%> (+3.38%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1076705...f95861f. Read the comment docs.

@yurishkuro
Copy link
Member

image

Use "resolves" or "closes" or "fixes", otherwise it's not being recognized by GitHub automatically.

@everett980
Copy link
Collaborator Author

everett980 commented May 21, 2019

Use "resolves" or "closes" or "fixes", otherwise it's not being recognized by GitHub automatically.

That explains why my previous PRs merely "mentioned" issues without closing them and I had to do it manually. Thanks!

Signed-off-by: Everett Ross <reverett@uber.com>
Copy link
Member

@tiffon tiffon left a comment

Choose a reason for hiding this comment

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

Looks great. Left a few comments, LMK what you think?

everett980 and others added 3 commits May 24, 2019 10:44
label for equivalent options

Signed-off-by: Everett Ross <reverett@uber.com>
state through mapStateToProps, Clean up global getJaegerUiConfig
warning suppression

Signed-off-by: Everett Ross <reverett@uber.com>
Copy link
Member

@tiffon tiffon left a comment

Choose a reason for hiding this comment

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

Looks great.

@tiffon tiffon merged commit 2abec69 into jaegertracing:master Jun 3, 2019
@everett980 everett980 deleted the issue-356-maximum-lookback-should-be-retention-period branch June 3, 2019 13:59
vvvprabhakar pushed a commit to vvvprabhakar/jaeger-ui that referenced this pull request Jul 5, 2021
)

Issue 356 maximum lookback should be retention period
Signed-off-by: vvvprabhakar <vvvprabhakar@gmail.com>
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.

The maximum search lookback should be the trace retention period
3 participants