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

add tracing spans #133

Conversation

austenLacy
Copy link

Description

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

@austenLacy austenLacy requested a review from shanth96 December 6, 2023 20:59
@austenLacy austenLacy force-pushed the austenlacy/vitess-project/add-more-spans-when-getting-connections branch from 191c10a to c62c2fa Compare December 6, 2023 21:00
austenLacy and others added 7 commits December 6, 2023 21:25
Signed-off-by: Austen Lacy <[email protected]>
Signed-off-by: Austen Lacy <[email protected]>
Signed-off-by: Austen Lacy <[email protected]>
Signed-off-by: Austen Lacy <[email protected]>
Signed-off-by: Austen Lacy <[email protected]>
@austenLacy austenLacy changed the title add spans in resource_pool.go add tracing spans Dec 12, 2023
Copy link

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale label Jan 12, 2024
Copy link

This PR was closed because it has been stale for 7 days with no activity.

@github-actions github-actions bot closed this Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants