-
Notifications
You must be signed in to change notification settings - Fork 5.5k
tracing: Deprecate OpenTracing #28987
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
Changes from 4 commits
eb7d249
4fa6849
68cd2ed
9debb03
c4f2db3
29a734c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,6 +18,8 @@ DynamicOpenTracingTracerFactory::DynamicOpenTracingTracerFactory() | |
| Tracing::DriverSharedPtr DynamicOpenTracingTracerFactory::createTracerDriverTyped( | ||
| const envoy::config::trace::v3::DynamicOtConfig& proto_config, | ||
| Server::Configuration::TracerFactoryContext& context) { | ||
| ENVOY_LOG_MISC(warn, "OpenTracing is deprecated and will be removed soon."); | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Shouldn't this be generated anyway via the use of the deprecated proto fields?
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh, fair point. I think I misread the suggestion on slack as saying we needed an explicit log in the factory. Reverted. |
||
|
|
||
| const std::string& library = proto_config.library(); | ||
| const ProtobufWkt::Struct& config_struct = proto_config.config(); | ||
| absl::StatusOr<std::string> json_or_error = MessageUtil::getJsonStringFromMessage(config_struct); | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An observation is that we could set a message-level deprecated annotation, but I'm guessing we would have to update some of the code for warning on this use of deprecated. Not strictly needed here, as to use this filter you need to set some stuff. But, for an empty filter config it would be needed in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I had exactly the same thought. I'm inclined to leave that out of this PR and address it if/when we have an empty filter config to deprecate.