- 
                Notifications
    You must be signed in to change notification settings 
- Fork 1k
Rename ktor tracing to ktor telemetry #12855
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
Conversation
0ef7bb4    to
    252db08      
    Compare
  
            
          
                ...ibrary/src/main/kotlin/io/opentelemetry/instrumentation/ktor/client/internal/Experimental.kt
              
                Outdated
          
            Show resolved
            Hide resolved
        
      3defa4a    to
    f646ba2      
    Compare
  
    4f5c848    to
    04d72e2      
    Compare
  
    8b7b2f3    to
    2c08222      
    Compare
  
    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.
I see no issues with this. Very generous deprecation for a non-stable component. 😁
        
          
                ...io/opentelemetry/instrumentation/ktor/v2_0/common/server/AbstractKtorServerTracingBuilder.kt
          
            Show resolved
            Hide resolved
        
      69a8841    to
    9397547      
    Compare
  
    | } | ||
| } | ||
|  | ||
| @Deprecated("Please use method `Experimental.emitExperimentalHttpClientMetrics`") | 
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.
I'm not sure this is needed as the class itself is deprecated. Also doesn't Experimental only work with the new telemetry builder class?
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.
I was trying to provide a hint where this method went since it's not obvious otherwise
        
          
                ...ain/kotlin/io/opentelemetry/instrumentation/ktor/v2_0/common/client/internal/Experimental.kt
              
                Outdated
          
            Show resolved
            Hide resolved
        
              
          
                ...ain/kotlin/io/opentelemetry/instrumentation/ktor/v2_0/common/client/internal/Experimental.kt
              
                Outdated
          
            Show resolved
            Hide resolved
        
      | internal lateinit var internalBuilder: DefaultHttpClientInstrumenterBuilder<HttpRequestData, HttpResponse> | ||
| protected lateinit var builder: DefaultHttpClientInstrumenterBuilder<HttpRequestData, HttpResponse> | 
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.
I couldn't figure out how to have both internal and protected access
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.
internal should be enough -- is there a reason why it shouldn't be public? It can only be used by other classes in this module when it's internal. 👍🏻
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.
I found a better way than duplicating the field, I created an internal accessor to the protected field
*KtorClientTracing*and*KtorServerTracing*have been deprecated and renamed to*KtorClientTelemetry*and*KtorServerTelemetry*Also moves everthing under ktor-2-common into
*.v2_0.common.*packagePart of #12846
See #12867 for change log migration notes entry