One of my favorite features of the Azure WebJobs SDK is the “Who wrote this blob?” feature. This is a common debugging scenario: you see your output is incorrect (in this case, a blob) and you’re trying to find the culprit that wrote the bad output.
On the main dashboard, there’s a “Search Blobs” button, which lets you enter the blob name.
Hit “Search” and then it takes you to a permalink for the function instance page that wrote that blob.
Of course, once you’re at the function instance page, you can then see things like that function’s input parameters, console output, and trigger reason for why that function was executed. In this case, the input blob was “in/a.txt”, and you can hit the “lookup” button on that to see who wrote the input. So you’re effectively tracing back up the chain.
And once you find the culprit, you can re-publish the function (if it was a coding error) or re-upload the blob (if it was a bad initial input) and re-execute it just the affected blobs.
It’s basically omniscient debugging for Azure with edit-and-continue.
How does it work?
When the WebJobs SDK invokes a function instance, it gives it a unique guid. That guid is used in the permalink to the function instance page. When a blob is written via [BlobOutput], the blob’s metadata is stamped with that guid. So the lookup only works for functions written by the WebJobs SDK.
What about queues?
The WebJobs SDK has a similar lookup queues. Queue messages written by [QueueOutput] also get stamped with the function instance guid and so you can lookup which function instance queued a message.