DX Application Performance Management

implemented the Mule fieldpack extension.   I would like to capture userid and the directives file from the extension simply states. 

# >>> Special feature to set the userid based on a HTTP Header Field
SetTracerParameter: RequestHandlerFrontendTracer userid.header.parameter user

Setting this to a header that is passed with a value in postman which invokes a mule listener does not reveal the userid in the transaction trace.   I can see the change is processed in autoprobe and my traces show the header as a property with a value.

My directive is set as follows

SetTracerParameter: RequestHandlerFrontendTracer test user

Guenter_Grossberger

tuusu01 hikodavis    any thoughts on this ? 

Chris:

    If you do not hear back by tomorrow, please open a case and the Support Engineer will get you an answer. Please m include this thread link

Thanks

Hal German

Chris: we will likely need to see the agent logs in verbose or debug mode to see what the tracer is actually doing and why it's missing the user ID.

If you can't upload here, please open a ticket and attach it there. let us know the ticket number so we can take a look.

attached along with an export of  a trace

Dear Chris:

    This is likely a bug and opening a case may be the best way to pursue. I asked some internal resources to take a look at what you provided so far . But it may take time for them to respond. 

Thanks

Hal German

01184064

Thanks Chris . Please report teh resolution to help others

I decompiled the extension and found that this is simply a syntax error on my part. 

the jar defines the following code ...

this.userIdHeaderField = parameters.get("userid.header.parameter");

This means that this is incorrect with test being my header field. 

SetTracerParameter: RequestHandlerFrontendTracer test user

This is the correct syntax

SetTracerParameter: RequestHandlerFrontendTracer userid.header.parameter test

This now works like a charm. 

Hiko_Davis