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.

Sign up for GitHub

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

Jump to bottom

Turn off the received-first-response traces #262

Open
3 tasks
SandGrainOne opened this issue Nov 15, 2024 · 0 comments
Open
3 tasks

Turn off the received-first-response traces #262

SandGrainOne opened this issue Nov 15, 2024 · 0 comments
Labels
status/blocked Further work depending on the completion of some other task/PoC/issue status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Nov 15, 2024 •
edited
Loading

Description

NOTE: This change requires a new version of the Npgsql package(s).

The default tracing from NpgSQL includes traces with the message received-first-response. There is a lot of them and we probably don't have any need for them.

Update nuget packages and turn off EnableFirstResponseEvent.

Additional Information

They're adding new options to the NpgsqlTracingOptions class. The one that is interesting for us is the EnableFirstResponseEvent property.
https://github.com/npgsql/npgsql/pull/5853/files#diff-e3555b1bea8f96895a00eff9a7462125d6224cd6fb1601be8d1562abf306f7aa

Tasks

  • Bump nuget packages with the necessary changes
  • Set EnableFirstResponseEvent to false

Acceptance Criteria

  • There are no received-first-response traces any longer
@SandGrainOne SandGrainOne added the status/draft Status: When you create an issue before you have enough info to properly describe the issue. label Nov 15, 2024
@olebhansen olebhansen added the status/blocked Further work depending on the completion of some other task/PoC/issue label Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
status/blocked Further work depending on the completion of some other task/PoC/issue status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olebhansen @SandGrainOne