Closed kbrockhoff closed 4 years ago
This is a great suggestion. let's start building a small list of contribs that we want to verify alpha:
HTTP:
gRPC:
JDBC: Wrappers for Driver and DataSource which in turn wrap Connection, Statement, PreparedStatement, CallableStatement
Spring Framework:
Spring Boot:
Logging: Population of logging context with current traceId and spanId for SLF4J and Apache Log4J2
Metrics adapters: Dropwizard, Micrometer
Eclipse MicroProfile: Integration with metrics, fault tolerance,
Resource retrievers: Major public cloud providers, k8s, major JEE app servers
@kbrockhoff could you please share/brainstorm any ideas on integration with MicroProfile metrics and fault tolerance?
We should also provide instrumentation for core java libraries (like https://github.com/opentracing-contrib/java-concurrent provides):
MicroProfile integration could include the export of metrics and events like those displayed in the Hystrix Dashboard such as RED, current circuit breaker status, bulkhead requests in waiting, retry counts, fallback counts.
Aggregated metrics from OpenTelemetry could also be read and used by circuit breaker open strategies and retry backoff strategies.
Closing this @kbrockhoff please re-open if you think the current instrumentation effort doesn't handle this yet.
Providing the equivalent of some of the OpenCensus contribs libraries would be useful in testing the usability of the APIs and the specification documentation while the APIs are still in alpha. I have already started this work and found a number of issues. See contribs-http branch here: https://github.com/kbrockhoff/opentelemetry-java/tree/contribs-http