JMS Headers

Elastic Observability APM
1

I am testing the JMS Plugin of Java Apm Client.

The jms agent plugin creates a trace header with elastic_apm_traceparent instead of elastic-apm-traceparent.

public interface JmsInstrumentationHelper<D, M, L> {

/**
 * In some cases, dashes are not allowed in JMS Message property names
 */
public static final String JMS_TRACE_PARENT_HEADER = TraceContext.TRACE_PARENT_HEADER.replace('-', '_');

@Nullable
Span startJmsSendSpan(D destination, M message);

@Nullable
L wrapLambda(@Nullable L listener);

}

So the reason is clear. But that's confusing in the programming.

2

@suikast42 is there something we can do to make this less confusing? It appears to be a limitation that we need to live with.

When https://github.com/elastic/apm/issues/71 is resolved (i.e. we start using the header "traceparent" everywhere), then I suppose this will be no longer be a problem.

3

That point missed in the documentation I think.

:+1:

4

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.