mpaul31

> This is a bug. We currently only apply the metrics if it comes from our logger that we pass in. We check the category/event pair. When you inject a...

The removal of this has a very large impact on many of our production apps that use change feed (cosmos db trigger) with exponential infinite retries. We obviously don't want...

@ealsur We use the following attribute on our change feed trigger method: `[ExponentialBackoffRetry(-1, "00:00:01", "00:00:10")]` It would be awesome if we could configure similar behavior on the `CosmosDBTrigger`.

@kshyju Any updates on the migration path or postponing the removal?

I get that but just like stage slots, which was in preview for a very (1+ years) long time, some adopt things sooner out of necessity. What about guidance then?...

Just to be clear, the retry policy/attribute does indeed work today aka with lease checkpointing working correctly. It appears it using an in memory retry policy similar to Polly.

@mathewc Is the app setting still a viable approach for v3 function apps? I also was told from an open MS ticket this when running deployment and swap operations, Azure...

> @mpaul31 yes, the app setting is still an option, so setting the host ID using `AzureFunctionsWebHost__hostId`(Windows and Linux) or `AzureFunctionsWebHost:hostId` (Windows only) is supported. @fabiocav Just to confirm, does...

awesome thx!

@joelhulen a retry would be necessary when an exception occurs during the processing of the document(s) on a change feed trigger. Could be transient or could be something more major...