Marie Hoeger

@dmontagu - cool project, thank you for it! Mind reviewing this quick PR?

@ColbyTresness - do you have any ideas on this? Based off of your closing of this issue: https://github.com/Azure/Azure-Functions/issues/393 +@pragnagopa as well who has done work to enable remote debugging.

@fabiocav and @brettsam - I'm guessing this isn't something we could enable now (breaking), but wondering if there is a clean workaround you can think of?

@HShather - I looked into those invocation ID's, and the inner details seem to point to unexpected behavior in the function code. The RpcException is caused by a Not Authenticated...

@HShather - I'll look into why the RpcException isn't showing fully in App Insights, but for now, here are the details: RpcException details Microsoft.Azure.WebJobs.Script.Rpc.RpcException : Result: Failure Exception: MongoError: Not...

@HShather - any updates on this issue?

@mathewc / @fabiocav / @paulbatum - This is a request similar to https://github.com/Azure/azure-functions-host/issues/4927 and others on adding some sort of filters to simplify logic for cross-cutting concerns. Marking as Triaged...

One thing we could do is to make that value added on premium-sku app creation when "node" is chosen? So far we only have that guidance documented here: https://docs.microsoft.com/en-us/azure/azure-functions/functions-premium-plan#memory-utilization-considerations

@pragnagopa - sorry that doc is specifically for premium SKU and guidance depends on which machines within premium SKU are selected. I think it's actionable, but not from our end...

Definitely fair! This isn't a requirement to run but an enhancement (node has one default max memory footprint) which is why I thought it would be better as a visible...