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

Fix OpenTelemetry REST client operation names as they changed upstream #1724

Merged
merged 1 commit into from
Mar 23, 2024
Merged

Fix OpenTelemetry REST client operation names as they changed upstream #1724

merged 1 commit into from
Mar 23, 2024

Conversation

michalvavrik
Copy link
Member

Summary

REST CLient operation names were changed here quarkusio/quarkus#39534. Changes is intentional.

Please select the relevant options.

  • Bug fix (non-breaking change which fixes an issue)
  • Dependency update
  • Refactoring
  • Backport
  • New scenario (non-breaking change which adds functionality)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@michalvavrik michalvavrik force-pushed the feature/fix-otel-context-propagation-operation-nanes branch from 0049ca1 to f61b02f Compare March 23, 2024 19:58
@michalvavrik michalvavrik merged commit 5a7d03d into quarkus-qe:main Mar 23, 2024
8 checks passed
@michalvavrik michalvavrik deleted the feature/fix-otel-context-propagation-operation-nanes branch March 23, 2024 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@gtroitsk gtroitsk gtroitsk approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@michalvavrik @gtroitsk