Azure-functions-durable-extension: Tracing not including input to signal

[mpaul31]

I have a durable entity that receives a signal and fires off an http request and does not mutate any internal state.

I have traceInputsAndOutputs set to true and when I look at my app insights logs I am not able to find the input that used when signaling the entity. Shouldn't this be traced?

Thanks!

[cgillum]

I took a look at the code and I think we should be correctly honoring the traceInputsAndOutputs setting (signals are internally implemented as external events). When this is not enabled, we simply show the number of bytes rather than the actual payload. Can you share a screenshot of what you're seeing in Application Insights?

[mpaul31]

sure.

[cgillum]

The prop__input field should represent the payload of the entity signals. We will say (null) like this if there is no payload associated with that event. Are you sure you're sending a non-null input with your signal?

[mpaul31]

yep definitely. i tested another entity that stores the input in the state and same result. i even added my own logging to verify it shows up in AI from within the signaled method.

[cgillum]

ok - thanks for confirming. I'll treat this as a logging bug that we need to investigate.

[mpaul31]

thank you.

[bachuv]

Hi @mpaul31, I took a look at this issue and wasn't able to reproduce it. Are you sure that this is running in Azure? I wasn't able to find any telemetry that correlated with the instanceId that you provided.

Can you provide the following information?

• The timestamp
• The entire trace message that you see in Application Insights including information about the state of the Entity (i.e. started, completed, etc.)

[mpaul31]

Hi @bachuv

Yes, I am sure 👍

Our environments are torn down all the time so I do not have the setting on at the moment in our dev environment so I'll work on getting a release out and provide the additional information.

One this worth mentioning is the input is an interface type not a concrete class (which works fine) and I use json converter to handle the deserialization.

[msftbot[bot]]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.