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

Debug Sentry Transactions #970

Merged
merged 9 commits into from
Dec 27, 2022
Merged

Debug Sentry Transactions #970

merged 9 commits into from
Dec 27, 2022

Conversation

bbengfort
Copy link
Collaborator

@bbengfort bbengfort commented Dec 26, 2022

Scope of changes

Updates the use of our interceptors for better Sentry handling.

Fixes SC-12088

Type of change

  • bug fix
  • new feature
  • documentation
  • other (describe)

Acceptance criteria

This is mostly a refactoring of our interceptors so that we chain them together more like standard middleware. However, we want to ensure that no part of our previous middlewares is missed and that the behavior of this new middleware should be the same as the old.

Author checklist

  • I have manually tested the change and/or added automation in the form of unit tests or integration tests
  • I have updated the dependencies list
  • I have recompiled and included new protocol buffers to reflect changes I made
  • I have added new test fixtures as needed to support added tests
  • Check this box if a reviewer can merge this pull request after approval (leave it unchecked if you want to do it yourself)
  • I have moved the associated Shortcut story to "Ready for Review"

Reviewer(s) checklist

  • Any new user-facing content that has been added for this PR has been QA'ed to ensure correct grammar, spelling, and understandability.

pkg/utils/sentry/config.go Outdated Show resolved Hide resolved
pkg/gds/interceptor.go Outdated Show resolved Hide resolved
pkg/trtl/interceptor.go Outdated Show resolved Hide resolved
}

func StreamType(info *grpc.StreamServerInfo) string {
if !info.IsClientStream && !info.IsServerStream {
Copy link
Contributor

Choose a reason for hiding this comment

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

Since this is only called in StreamLogging, which only accepts grpc.ServerStreams, do we really need to check here for unary RPC's?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think we do - if we don't handle all cases of the different combination of bools then the default will be "bidirectional" and that's not the case when they're both false.

@bbengfort
Copy link
Collaborator Author

@pdamodaran @DanielSollis I've made the changes you've requested and I believe I've fixed the tests as well.

@bbengfort bbengfort merged commit 2a792ee into main Dec 27, 2022
@bbengfort bbengfort deleted the sc-12088/trtl-sentry-tx branch December 27, 2022 22:40
DanielSollis pushed a commit that referenced this pull request Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants