Are WebJobs relying on best-effort storage analytics?

Question

I'm trying to understand how WebJobs works to determine whether it's something we can use. I've only played around with it for an hour so I'm by no means an expert.
I've created a small simple web job which just processes blobs in a specific container, like this:
public static void ProcessBlob([BlobTrigger("container/{name}")] TextReader input, string name)
string s = input.ReadToEnd();
It runs fine in a console app I use for testing. I use Fiddler to monitor the http traffic it produces.
In Fiddler I see that it accesses the $logs container in the storage account. If I understand everything correctly, the data in this container is generated by Storage Analytics described here:
http://msdn.microsoft.com/library/azure/hh343262.aspx
When reading that page about storage analytics, I see the following statement:
"Requests are logged on a best-effort basis."
It sounds to me like there's no guarantee that all requests will be logged and it's not really clear what may
cause it to fail. And if I understand WebJobs properly, it relies on all requests being logged. So
the picture I get is that WebJobs are "best-effort" as well and sometimes it might not be executed for blobs.
Is my understanding correct, or am I missing something?
Nitramafve

Answer 1

Thanks Girish!
Also thanks Frank, but what you write does not seem to be entirely correct. I understand that WebJobs are a piece of code that can be run on demand. But before starting to use it, I wanted to understand exactly how WebJobs actually works. I've been
working with Azure Storage for 4 years and know that there is no documented robust way to get notifications when a change is made to blob storage. Based on that, it seemed to me that implementing WebJobs on top of Azure Storage would be hard, unless there
were some undocumented Azure services it was relying on.
So I digged into the Azure WebJobs source code and monitored its request towards Azure Storage, and saw that it was relying on Azure Storage Analytics logs to determine what blobs have been created/updated (so that it can trigger the code execution). Internally
within the Azure WebJobs SDK assemblies, there's code which is designed to parse Azure Storage Analytics (the class StorageAnalyticsLogParser)
This is what does not add up. Azure WebJobs appars to be relying on Azure Storage Analytics, but Azure Storage Analytics is documented as best-effort, which would mean that Azure WebJobs would not always work properly.
But I'm sure I'm missing something here. Maybe Storage Analytics is actually "robust" and not best-effort.
Nitramafve