Getting the instance id of a running Azure Function with ExecutionContext.InvocationId

Getting the instance id of a running Azure Function with ExecutionContext.InvocationId

Recently I had a discussion about Azure Functions, the pros and cons, and running multiple instances of batch processing simultaneously. One of the immediate questions that came up in that discussion was; In the built-in logs you see in the streaming log service or in the log console, how do you know which message comes from what invocation? Great question, let's dig into that! Get the Invocation Id of an instance of a Azure Function When a Function runs, it gets a new unique identifier by default. You can see this in the invocation log: 2016-12-01T22:34:34.605 Function…

Read More

Reuse your C# Script (csx) code in multiple Azure Functions

Reuse your C# Script (csx) code in multiple Azure Functions

Azure Functions hit GA (General Availability) recently. A big milestone for the Azure Functions team, and I'm happy to see that it's finally out of Preview. Lately I've been working a lot with various parts of Azure to find the best fit for various busines cases. Functions has been one of those adventures, doing a lot of R&D around how they can be put to good use. One of the pitfalls I found early on was that I wanted to have multiple functions process different things on the same "task". With that I also had various…

Read More