Trask Stalnaker
Trask Stalnaker
> 1. I'll make a contribution that provides dynamic update capability. It will have a code API. That's separate - we can discuss the actual implementation, API and capability when...
cc @marychatte
> I'm testing this using version 2.6.0 of the opentelemetry-instrumentation-api artifact. are you also using the Java agent?
Since there has been no activity on this enhancement for the past year we are closing it to help maintain our backlog. Anyone who would like to work on it...
Closing as there does not appear to be engagement from the necessary folks in order to move this forward at this time.
related: https://github.com/open-telemetry/opentelemetry.io/issues/6102#issuecomment-2620284280 > I'm optimistic about future [weaver](https://github.com/open-telemetry/weaver) developments to address this need [Instrumentation API] for end users
linking in related(?) issue #5995
Closing as there does not appear to be engagement from the necessary folks in order to move this forward at this time.
it looks like we have some of both currently: ### `status` * `deployment.status` * `k8s.container.status.last_terminated_reason` * `metric.hw.status` * `signalr.connection.status` * `system.process.status` * `system.processes.status` * `test.case.result.status` * `test.suite.run.status` ### `state` *...
> launch your application with `OTEL_JAVAAGENT_EXTENSIONS` env variable pointing to something that doesn't exist : you won't get any particular warning in the logs. logging a warning in this case...