Regarding magazines:
For continuous WebJobs, Console.Out and Console.Error are routed to the "application logs", they will be displayed as a repository of files, blocks or tables depending on the configuration of the application logs (similar to your site).
Also, the first 100 lines in each call also fall into the WebJob log file (to ease the debugging pain when WebJob crashes on startup), accessible through the Azure portal (but also stored in the file system of the site on data / workstations / continuous / JobName).
For launched / scheduled WebJobs, Console.Out / Console.Error is routed to the WebJobs startup log file, also accessible using the Azure portal and stored in data / jobs / triggered / jobName / runId.
Console.Out is handled (marked) as INFO and Console.Error as ERROR.
Regarding connection strings:
You can access your connection strings in the same way as on your website using the ConfigurationManager class for WebJobs not written in .NET, you can find these connection strings (and application parameters) as environment variables (anyway as on your website).
Amit Apple Mar 15 '14 at 6:26 2014-03-15 06:26
source share