Steve Rao

> cc @chickenlj @steverao @ruansheng8 I think we can set some rules to do it.

Something showed,like this "The web application [ROOT] appears to have started a thread named [com.alibaba.nacos.client.naming.updater]这个报错日志没有关系，你是出现了应用不能正常停止吗？

As far as I know, the conventions of http client and server are stabled. For the issue, is there any plan?@open-telemetry/java-instrumentation-approvers

> yes, it's a step in the direction. The config properties are the same now, but the builders still don't implement a common interface. If there are some remaining tasks...

This is our plan to stabilize HTTP instrumentation https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/12846. If anyone is interested in them, welcome to join us!

I found this might be a sentinel problem. My test codes as below: ``` @GetMapping("/rt") public String rt() { return restTemplate.getForObject("https://httpbin.org/delay/1", String.class); } # degrade rule { "resource": "/rt", "count":...

> I would support this, some kind of SPI that a Java agent extension could use to add these things to the existing instrumentations > > cc @steverao @ralf0131 who...

> Ktor 3.0.0 is released Yes, we noticed it. [We'd welcome a contribution for this](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/ISSUES.md#contribution-welcome).

> I don't wish to change anything in the oshi instrumentation in this PR. Are you going to change them in following other PR or other reason?