Azure-functions-durable-extension: Suppress unnecessary dependency tracking for internal storage calls.

[kashimiz]

Prompted by this StackOverflow post: Currently, Application Insights' dependency tracking feature reports 404 responses from Azure Storage such the initial call made by table.CreateIfNotExists() when the table doesn't exist, which is part of the Durable Functions extension's program flow. We should suppress these to reduce noise in customer's App Insights logs.

[JohnReeson]

Link one identical issue.

[oising]

This one is bothering my app insights OCD.

[ProjectPete]

Bump!
+1 oising!

It's a distracting red, please make this tweak, or advise us on a work-around.

We need a clearer vision for 2020! :D

Apart from these tiny issues... I'm flippin' lovin' Function Apps, and the monitoring/logs around them...

A true game changer. Interesting times...

Happy New Year to all durable devs & digital devotees x

[hugobarona]

Definitely I am looking forward to this change since the 404 dependency errors are really distracting, especially when i am using Live Metrics Stream in the functions in Production while executing several requests per minute.

[cgillum]

@amdeel this might be a good one for you to look into. Here is a StackOverflow post that describes how to do this for SQL (we would need to do one slightly differently - i.e. for Azure Storage calls): https://stackoverflow.com/questions/38320886/app-insights-disable-sql-dependency-telemetry

@brettsam would be a great person to consult with on this as well.

[shelbaz]

Bump. Looking forward to this update, too many false positive errors in ApplicationInsights because of it.

[ConnorMcMahon]

Don't want to delay 2.2.0 for this, so targeting 2.2.1.

[ConnorMcMahon]

punting for 2.3.0

[corwestermaniddink]

Update please?

[oising]

La la la la la la

[ravibha]

We are facing a similar issue as well. Seeing 404 dependency failures when durable functions are being executed. Dependency type is 'Azure Table'. Has this been fixed already? I was not able to tell from the backlog item.

Thanks!

[cgillum]

This is not fixed yet. I realize this is likely very annoying, so apologies for the delays in getting around to this. It's in our backlog.

[tanujnarula]

@cgillum @oising

Hello Chris,

Main problem is, we went ahead and created "SuppressAzureTableTelemetryProcessor" to suppress this 404 error but to find out that web job sdk's function "AddApplicationInsightsWebJobs" does not support adding this processor and this ITelemetryProcessor wont be triggered. So we are at loss how to handle this now?

We also tried adding it using "services.AddApplicationInsightsTelemetryProcessor();", but it wont trigger or use it.

Here is the issue which I refer.
https://github.com/Azure/azure-webjobs-sdk/issues/2584

Any further suggestions?

Regards
Sam.

[tanujnarula]

Hello Folks, @cgillum @oising
Any feedback on the issue mentioned just above?

[AndiHahn]

Hi @cgillum @ConnorMcMahon ,
When this issue will be fixed? Is there any workaround to suppress these errors?
It's spamming my application insights and makes it hard to figure out real failures.

[ConnorMcMahon]

We will prioritize this for our 2.4.0 release, as this should be simple to fix and there is clearly some pain points here.

[amdeel]

To be transparent here, we've been blocked on this work. Like stated above, we do not have the ability to add ITelemetryProcessors at this time.

However, I'm going to do some further investigation on this work to see if we can suppress these 404s another way.

[akw123]

getting spammed by this error as well. Hope the team able to push this in soon.
It has impacted our ability to pinpoint failures.

[ConnorMcMahon]

We have a PR out for this that we hope to get released in the very near future.