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

Deduplicate tags for spans #375

Merged
merged 4 commits into from
May 16, 2019
Merged

Conversation

rubenvp8510
Copy link
Collaborator

@rubenvp8510 rubenvp8510 commented May 3, 2019

Signed-off-by: Ruben Vargas [email protected]

Which problem is this PR solving?

Short description of the changes

  • I check for duplicated tags, and remove it (I left only one of them)
  • Also has a boolean to indicate that span has duplicated tags so we can show a warning or something

Screenshot of warning:

Screenshot from 2019-05-03 12-29-02

@codecov
Copy link

codecov bot commented May 3, 2019

Codecov Report

Merging #375 into master will increase coverage by <.01%.
The diff coverage is 95.12%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master     #375      +/-   ##
==========================================
+ Coverage   88.71%   88.72%   +<.01%     
==========================================
  Files         157      159       +2     
  Lines        3518     3556      +38     
  Branches      802      811       +9     
==========================================
+ Hits         3121     3155      +34     
- Misses        362      365       +3     
- Partials       35       36       +1
Impacted Files Coverage Δ
...ePage/TraceTimelineViewer/VirtualizedTraceView.tsx 92.37% <ø> (ø) ⬆️
...ts/TracePage/TraceTimelineViewer/SpanDetailRow.tsx 100% <ø> (ø) ⬆️
...age/TraceTimelineViewer/SpanDetail/DetailState.tsx 95.83% <100%> (+0.83%) ⬆️
...TracePage/TraceTimelineViewer/SpanDetail/index.tsx 100% <100%> (ø) ⬆️
...cePage/TraceTimelineViewer/SpanDetail/TextList.tsx 100% <100%> (ø)
.../components/TracePage/TraceTimelineViewer/duck.tsx 98.4% <100%> (+0.05%) ⬆️
...kages/jaeger-ui/src/model/transform-trace-data.tsx 84.61% <91.66%> (+1.59%) ⬆️
...e/TraceTimelineViewer/SpanDetail/AccordianText.tsx 92.3% <92.3%> (ø)
...eViewer/TimelineHeaderRow/TimelineViewingLayer.tsx 88.13% <0%> (-3.39%) ⬇️
... and 1 more

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 bfd32be...6e67ca2. Read the comment docs.

@rubenvp8510 rubenvp8510 changed the title [WIP] Deduplicate tags for spans Deduplicate tags for spans May 3, 2019
@rubenvp8510 rubenvp8510 force-pushed the deduplicate-tags branch 2 times, most recently from b008e31 to dcfa684 Compare May 3, 2019 18:27
@yurishkuro
Copy link
Member

I like the warning icon, but we have a built-in place for warnings in the spans (below), which may contain more than one warning. So it would be better to display them as a list. Maybe we can add another expandable item below logs called Warnings({count}), which may be prefixed with the warning icon for better visuals, and not show up at all if span has no warnings.

https://github.com/jaegertracing/jaeger/blob/3fff10206109b54c9d8a42cb1347336836a9b0ea/model/model.pb.go#L359

@rubenvp8510
Copy link
Collaborator Author

Ahh! I haven't noticed that field in span object, in that case it makes more sense to put warnings there. I'll do the modifications and update this PR, with new screenshots also.

@rubenvp8510
Copy link
Collaborator Author

Screenshot from 2019-05-04 13-09-57

@yurishkuro WDYT?

@rubenvp8510 rubenvp8510 force-pushed the deduplicate-tags branch 11 times, most recently from ac17f3f to a4bca89 Compare May 5, 2019 15:03
@yurishkuro
Copy link
Member

@rubenvp8510 s/s looks good to me. I assume the Warnings will not show up if there are no warnings?

@tiffon is this ready to merge?

@rubenvp8510
Copy link
Collaborator Author

@yurishkuro yes, the warning accordion does not show up if there are no warning on the span

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.

This looks great! Thank you!

I left a few comments. LMK if any look awry.

I experimented a bit with the styling, to see what it would look like using color instead of the icon:

Screen Shot 2019-05-14 at 10 49 10 PM

Screen Shot 2019-05-14 at 10 51 06 PM

Screen Shot 2019-05-14 at 10 53 21 PM

Screen Shot 2019-05-14 at 10 54 08 PM

Screen Shot 2019-05-14 at 10 54 35 PM

What do you think?

Thank you again, and apologies for the delay in reviewing!

@@ -24,6 +24,7 @@ limitations under the License.
color: inherit;
display: block;
padding: 0.25rem 0.5rem;
padding-left: 0;
Copy link
Member

Choose a reason for hiding this comment

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

The left padding allows the log section chevron to align with the chevrons from the individual log messages. Setting padding-left: 0 causes a misalignment.

Screen Shot 2019-05-14 at 12 08 13 PM

Before:

Screen Shot 2019-05-14 at 12 06 55 PM

@@ -56,7 +56,7 @@ export default function AccordianLogs(props: AccordianLogsProps) {
}

return (
<div className="AccordianLogs">
<div className="AccordianLogs ub-mb1">
Copy link
Member

Choose a reason for hiding this comment

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

Instead of adding a util class please add the style to the .AccordianLogs class. I try to only use util styles when the element is not already being styled via a CSS class specific to that element.

u-simple-scrollbars is the main exception.

padding: 0.25rem 0.5rem;
}

.TextList-row:nth-child(2n) > td {
Copy link
Member

Choose a reason for hiding this comment

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

Looks like there is a missing second -

.TextList--row:nth-child(2n)

vertical-align: baseline;
}

.TextList--row > td {
Copy link
Member

Choose a reason for hiding this comment

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

I think this is a dupe of the style on line 37 and can be removed?

packages/jaeger-ui/src/model/transform-trace-data.tsx Outdated Show resolved Hide resolved
packages/jaeger-ui/src/types/trace.tsx Outdated Show resolved Hide resolved
Signed-off-by: Ruben Vargas <[email protected]>
@rubenvp8510
Copy link
Collaborator Author

rubenvp8510 commented May 15, 2019

Hi @tiffon I did all requested modifications, also I modified the style according to your suggestion, I think looks better and more "inline" with the actual UI style.

I attached some screen-shots of the latest modifications.

Screenshot from 2019-05-15 18-23-30
Screenshot from 2019-05-15 18-23-19

Could you please review again? Thank you a lot!

@ghost ghost assigned tiffon May 16, 2019
@ghost ghost added the review label May 16, 2019
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! Awesome.

I pushed a couple of styling tweaks, mostly adding a bottom border to the warnings header, when it's open, setting its content to a light grey background, and adding a headerClassName prop so the CSS styles aren't coupled to the AccordingText implementation.

Screen Shot 2019-05-15 at 10 20 55 PM

Let me know if anything about those changes look awry...?

@rubenvp8510
Copy link
Collaborator Author

Looks very good! Thanks for the improvement!

@tiffon
Copy link
Member

tiffon commented May 16, 2019

Hey, awesome, done! 👍

@tiffon tiffon merged commit 126f42c into jaegertracing:master May 16, 2019
@ghost ghost removed the review label May 16, 2019
vvvprabhakar pushed a commit to vvvprabhakar/jaeger-ui that referenced this pull request Jul 5, 2021
Deduplicate tags for spans
Signed-off-by: vvvprabhakar <[email protected]>
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.

3 participants