Skip to content

feat: log records in a new tab #916

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

Merged
merged 14 commits into from
Jun 17, 2021
Merged

feat: log records in a new tab #916

merged 14 commits into from
Jun 17, 2021

Conversation

itssharmasandeep
Copy link
Contributor

Description

log records in a new tab

Testing

Local testing done!!

Checklist:

  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been merged and published in downstream modules

Screenshot 2021-06-09 at 6 27 31 PM

@itssharmasandeep itssharmasandeep requested a review from a team as a code owner June 9, 2021 13:01
@github-actions

This comment has been minimized.

@codecov
Copy link

codecov bot commented Jun 9, 2021

Codecov Report

Merging #916 (f7f9b9f) into main (5de8ca7) will increase coverage by 0.07%.
The diff coverage is 83.83%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main     #916      +/-   ##
==========================================
+ Coverage   85.14%   85.21%   +0.07%     
==========================================
  Files         806      812       +6     
  Lines       16644    16714      +70     
  Branches     2098     2003      -95     
==========================================
+ Hits        14171    14243      +72     
+ Misses       2441     2439       -2     
  Partials       32       32              
Impacted Files Coverage Δ
.../pages/trace-detail/trace-detail.page.component.ts 41.66% <0.00%> (+11.66%) ⬆️
...ed/components/span-detail/span-detail.component.ts 100.00% <ø> (ø)
...pi-trace-detail/api-trace-detail.page.component.ts 38.46% <0.00%> (+14.65%) ⬆️
...omponents/log-events/log-events-table.component.ts 70.00% <42.85%> (-7.78%) ⬇️
...rc/pages/trace-detail/logs/trace-logs.component.ts 60.00% <60.00%> (ø)
.../api-trace-detail/logs/api-trace-logs.component.ts 60.00% <60.00%> (ø)
.../trace-detail/sequence/trace-sequence.component.ts 62.50% <62.50%> (ø)
...ce-detail/sequence/api-trace-sequence.component.ts 62.50% <62.50%> (ø)
.../trace-detail/sequence/trace-sequence.dashboard.ts 100.00% <100.00%> (ø)
...src/pages/trace-detail/trace-detail.page.module.ts 100.00% <100.00%> (ø)
... and 17 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 5de8ca7...f7f9b9f. Read the comment docs.

@github-actions

This comment has been minimized.

@Component({
changeDetection: ChangeDetectionStrategy.OnPush,
template: `
<ng-container *ngIf="this.logEvents$ | async as logEvents">
Copy link
Contributor

Choose a reason for hiding this comment

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

If we are fetching from graphql then we should use *htLoadAsync so that we can show the loader icon

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Actually, for this
Data is already being fetched before this, on the page level. and here it will be only used as a static data observable (shareReplay)

Copy link
Contributor

Choose a reason for hiding this comment

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

okay. I hope that doesn't change :)

Copy link
Contributor

Choose a reason for hiding this comment

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

It is better to use loadAsync. If in case fetchLogEvents starts returning a new observable, we would have to remember to update this template as well.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@@ -221,7 +226,8 @@ describe('Trace Waterfall data source model', () => {
displaySpanName: 'Span Name 2',
serviceName: 'Service Name 2',
type: SpanType.Exit,
spanTags: {}
spanTags: {},
logEvents: []
Copy link
Contributor

Choose a reason for hiding this comment

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

We could add properties so that the test becomes relevant :)

anandtiwary
anandtiwary previously approved these changes Jun 16, 2021
Copy link
Contributor

@anandtiwary anandtiwary left a comment

Choose a reason for hiding this comment

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

Looks good. Please test the two pages in ht-ui and t-ui before merging.

@github-actions

This comment has been minimized.

@aaron-steinfeld
Copy link
Contributor

Some suggestions based on offline conversation (haven't reviewed most of PR, will leave that to others): #935

@github-actions

This comment has been minimized.

</ng-container>
`
})
export class TraceLogsComponent {
Copy link
Contributor

Choose a reason for hiding this comment

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

So this is not a dash page. It works. But I am not sure if we should be diverge from the dashboard pattern.

@aaron-steinfeld thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

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

IMO, we should try to reign dashboards back in to pages that look like dashboards. If we later need to embed this as a widget in another page, we could widgetize it for sharing at that point - but no need to build these custom single-page, single-purpose widgets.

anandtiwary
anandtiwary previously approved these changes Jun 16, 2021
@github-actions

This comment has been minimized.

@itssharmasandeep itssharmasandeep merged commit 3d7da37 into main Jun 17, 2021
@itssharmasandeep itssharmasandeep deleted the log-tab branch June 17, 2021 17:27
@github-actions
Copy link

Unit Test Results

    4 files  ±0  259 suites  +1   13m 57s ⏱️ -28s
936 tests +7  936 ✔️ +7  0 💤 ±0  0 ❌ ±0 
942 runs  +7  942 ✔️ +7  0 💤 ±0  0 ❌ ±0 

Results for commit 3d7da37. ± Comparison against base commit 5de8ca7.

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.

4 participants