Please answer these questions before submitting your issue.

• Why do you submit this issue?
• [] Question or discussion
• Bug
• Requirement
• Feature or performance improvement

Question

org.springframework.kafka.KafkaListenerEndpointContainer#0-4-C-1 InstMethodsInter : class[class org.postgresql.jdbc.PgPreparedStatement] before method[executeWithFlags] intercept fai

VERSION: v1.14.0
EXPECTATION: single trace response in UI for tag search guid:x-request-id=628d36f4-9072-c587-3b00-804c10a63000

ACTUAL: No trace results. Try another query.
SETUP:

1. To easily get data populated I modified this file `plugin/storage/badger/spans

Requirement - what kind of business use case are you trying to solve?

Configuration that can affect service performance and would ideally live and be deployed with the service code & configuration.

For example, debugging an individual service issue might start with a focus on the service itself. At the moment, remote sampling strategies could be configured remotely. One might not think to

The current OpenTelemetry.Instrumentation.SqlClient package can be used to instrument MSSQL clients; could a new package be added for Postgresql (Npgsql.EntityFrameworkCore.PostgreSQL) or perhaps a more general Entity Framework Core instrumentation library?

Locally i've refactored the current SqlClient instrumentation to make it work more generally with Microsoft.EntityFrameworkCore diagnosti

Requirement - what kind of business use case are you trying to solve?

can we change the default choice of layout selection to be one node per resource in this section:

Current default is `sho

open-telemetry/opentelemetry-specification#722

Spec now has a single definition for attributes shared with resources and traces. Where applicable, ensure that our span attributes and resource attributes conform to required limitations.

@thegryfon noticed that in community axios implementations, some leak contexts and you wouldn't necessarily know until a second root trace is attempted.

here's an example scenario I think tests could cover:

there is no parent trace in scope
create a client request
create a second client request
verify that both client requests are root spans

See: #1482

Cannot use same trace ID accross different node of microservices

On the document of https://opentracing.io/docs/overview/tracers/#propagating-a-trace-with-inject-extract, there is a concept of inject and extract. This is working fine with http carrier. Yet, I cannot reproduce this with Text Map carrier.

Please create a doc for u