René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Java-Logging: OpenTelemetry spans are ignored as parents for LogRecords","articleBody":"Tracking the same issue as https://github.com/googleapis/google-cloud-go/issues/9302 to propagate correct TraceId and SpanId for logging and tracing correlation.\r\n\r\n**Client**\r\n[java-logging](https://github.com/googleapis/java-logging)\r\n\r\n**Context**\r\nIn java-logging libraries, the current implementation will always use a remote trace ID and span ID parsed from HTTP headers that originate from outside the application.\r\n\r\n**Expected behavior**\r\nIf the user is using opentelemetry instrumentation, we want to use the traceID and spanID of the span that OpenTelemetry created. This way, when a user looks for logs associated with that span, the logs produced by this logging library will appear.\r\n\r\n**Design Docs:**\r\n[OpenTelemetry Trace/Span ID Support in Cloud Logging Library](http://goto.google.com/logging-otel-span-support)\r\n[OpenTelemetry Trace/Span ID Support in Java Cloud Logging Library](http://go/logging-otel-span-support-java)","author":{"url":"https://github.com/cindy-peng","@type":"Person","name":"cindy-peng"},"datePublished":"2024-04-30T09:49:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/1595/java-logging/issues/1595"}