You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should consider providing a config based way for customers to opt out of the default dependency logging the worker does on function invocations (code here). These logs show up as "Invoke" internal dependencies:
Currently the only way for customers to remove these Invoke dependency logs is to write a custom telemetry processr, as in this sample:
publicclassCustomTelemetryProcessor:ITelemetryProcessor{privateITelemetryProcessorNext{get;set;}// Link processors to each other in the chain.publicCustomTelemetryProcessor(ITelemetryProcessornext){this.Next =next;}publicvoidProcess(ITelemetrytelemetry){if(telemetry is DependencyTelemetry dependency && dependency.Name =="Invoke"){// Do not send telemetry for the "Invoke" dependency.return;}// Call the next processor in the chain.this.Next.Process(telemetry);}}
Description
We should consider providing a config based way for customers to opt out of the default dependency logging the worker does on function invocations (code here). These logs show up as "Invoke" internal dependencies:
Currently the only way for customers to remove these Invoke dependency logs is to write a custom telemetry processr, as in this sample:
This came up recently in CRI https://portal.microsofticm.com/imp/v5/incidents/details/564586958/summary.
The text was updated successfully, but these errors were encountered: