Hi, We are getting 2 different field names for the...
# general
m
Hi, We are getting 2 different field names for the same parameter from the source. messaging.message_payload_size_bytes comes in one trace, messaging.message.payload_size_bytes comes in another trace. The difference here is _ & . in these fields. We are using 0.55.0 version of the OTEL collector. Pls let me know whether this issue resolved in the agent ? Any other fields have the similar issue ? Few details about the versions: "key" : "telemetry.auto.version", "value" : { "stringValue" : "1.18.0" } }, { "key" : "telemetry.sdk.language", "value" : { "stringValue" : "java" } }, { "key" : "telemetry.sdk.name", "value" : { "stringValue" : "opentelemetry" } } "scope" : { "version" : "1.18.0-alpha", "name" : "io.opentelemetry.kafka-clients-0.11" } { "key" : "process.executable.path", "value" : { "stringValue" : "/usr/local/openjdk-11binjava" } }, { "key" : "process.pid", "value" : { "intValue" : "1" } }, { "key" : "process.runtime.description", "value" : { "stringValue" : "Oracle Corporation OpenJDK 64-Bit Server VM 11.0.12+7" } }, { "key" : "process.runtime.name", "value" : { "stringValue" : "OpenJDK Runtime Environment" } }, { "key" : "process.runtime.version", "value" : { "stringValue" : "11.0.12+7" } }
a
@nitya-signoz please have a look
n
Hi @manohar mirle , you are using the Java agent to collect your traces right ?
Hi @manohar mirle, can you share the version of java agent that you are using to collect your traces. Also just to clarify you are facing this issue in your traces right ?
m
Hi @nitya-signoz Here is the agent details: -javaagent:/tmp/telemetry/opentelemetry-javaagent.jar { "key" : "process.executable.path", "value" : { "stringValue" : "/usr/local/openjdk-11binjava" } { "key" : "process.runtime.description", "value" : { "stringValue" : "Oracle Corporation OpenJDK 64-Bit Server VM 11.0.12+7" } }