Wake up Azure Function

1
votes

I have an existing Azure Function that is on a consumption plan

I am writing another function which will call this

Once the existing function is running, it processes files in storage account.

In order the files in my storage account to be processed, we have to manually go into the portal and "wake up" the function by navigating

Is there a way to do this via C# code?

This function is hosted on a consumption based plan

2
c#azureazure-devopsazure-functionsserverless
Azure Functions are automatically woken up based on their triggers (e.g. timer, http). There is no requirement to do this manually. What are the defined triggers for each of these functions at the moment? – sellotape
Not sure how to check this? One of the functions will be new one inside in a different function app. E.g. FunctionApp1.Function1 will call FunctionApp2.Function1 – Paul
If they’re written in C#, you should see the function entry point decorated with a Trigger attribute indicating the trigger type. You should look into the various trigger options, as e.g. a blob arriving in blob storage is one of them and might fit what you’re trying to do with a single function. – sellotape

2 Answers

1
votes

May be this is exact solution you are looking for. I came across this article "An Azure Function to keep other Functions/URLs warmed up" while looking for such solution, haven't tried it yet but I will. If you try it first do post the result.

https://www.sharepointnutsandbolts.com/2018/09/Azure-Function-Warmup-Cold-Start.html

The other approach that I came across is "pinging a health endpoint within your Azure Functions through Azure Monitor." Create a URL ping test. https://docs.microsoft.com/en-us/azure/azure-monitor/app/monitor-web-app-availability

I am in the process of trying these out. Hope this helps.

0
votes

In serverless computing, Azure functions get executed/spin up whenever you make an invoke, if you want to call another function inside a function you can do via HTTP call.

Durable Functions lets you write stateful functions in a serverless environment. There's nothing built-in in Function Apps to call one HTTP function from other functions without actually making the HTTP call paticularly Function Chaining.