azure-webjobs

问题 I have a continuous WebJob deployed via the Kudu API to /api/continuouswebjobs/{job name} as outlined here. The App Service I'm deploying to has just a single instance running. On occasion it's looking like the previous version of a WebJob is not removed following a deployment and it runs concurrently with the new version. This can continue to occur and I've seen up to nine processes running concurrently. Application names redacted but they are identical for each process: Stopping the WebJob

问题 After my yesterday's question (Continuous WebJobs and CancellationToken) I thought now I've understand the handling of continuous WebJobs and graceful shutdown and did some testing. Additional Info With https://myWebJob.scm.azurewebsites.net/api/continuouswebjobs I get: { [some info ommited...] "type": "continuous", "error": null, "using_sdk": true, "settings": { "stopping_wait_time": 120 } } At Thu, 31 Dec 2015 07:00:23 GMT I put a Stop to the Server, the following entries in the Dash Board

问题 The question is specific to WebJobs. I've been thru the steps to configure logging to my Azure WebSite (sry...Azure AppService WebSite - sheese with the name changes already) and am now trying to iron everything out for WebJobs running beneath the same. I'm logging to both a RollingFile and to the Ado.net appender - for sake of brevity pasting config only for the File - neither of the 2 work so gotta be a problem common at the core. The sub-directory specified in the config exists but files

问题 I have an azure webjob that runs continuously. I'd like to be notified if it stops or is aborted. Is there an event that gets called on stop or abort that I can trigger an email? Thanks! 回答1: If you're using the WebJob SDK, then you can do that using the new ErrorTrigger and SendGrid extensions. Check this wiki on how to set that up. But here is a sample code (copied from the wiki above) that uses both extensions to send an email if an error occurred 10 times in 30 minutes window with a

问题 I have the following functions in the same web job console app that uses the azure jobs sdk and its extensions. The timed trigger queries an API end point for a file, does some additional work on it and then saves the file to the blob named blahinput. Now the second method "ProcessBlobMessage" is supposed to identify the new blob file in the blahinput and do something with it. public static void ProcessBlobMessage([BlobTrigger("blahinput/{name}")] TextReader input, string name, [Blob(

问题 I was hoping if someone can clarify a few things regarding Azure Storage Queues and their interaction with WebJobs: To perform recurring background tasks (i.e. add to queue once, then repeat at set intervals), is there a way to update the same message delivered in the QueueTrigger function so that its lease (visibility) can be extended as a way to requeue and avoid expiry? With the above-mentioned pattern for recurring background jobs, I'm also trying to figure out a way to delete/expire a

问题 We have a webapp deployed with a production slot and a development slot, for both we've created several webjobs (both continuous and scheduled) and we want to deploy them manually (without being linked to the webapp deploy) so the process we follow for deployment is: 1 -> Deploy WebApp 2 -> For each WebJob: Right Click on the project + Deploy as Azure WebJob + Select proper slot + Publish We are able to publish for the production slot without any problems, but when it comes to the development

问题 This question already has answers here : How do I write to the logs in Azure WebJobs from a C# console app? (2 answers) Closed 3 years ago . So I have tried: Trace.TraceInformation("Trace.Information Found message on queue"); Debug.WriteLine("Debug Found message on queue"); Trace.WriteLine("Trace.WriteLine Found message on queue"); Console.WriteLine("Console.WriteLine Found message on queue"); But neither of them outputs to the Azure portal Web Jobs output log. What am I missing? 回答1: Later

问题 I'm not being able to publish a scheduled WebJob to Azure App Service. I'm using Visual Studio 2017. With this settings all works fine: { "$schema": "http://schemastore.org/schemas/json/webjob-publish-settings.json", "webJobName": "WebJobName", "runMode": "OnDemand" } But when I set this settings: { "$schema": "http://schemastore.org/schemas/json/webjob-publish-settings.json", "webJobName": "WebJobName", "startTime": "2017-03-17T07:00:00+00:00", "endTime": "2027-03-17T07:00:00+00:00",

问题 I am wondering about how it might be possible to deploy a Node.js app on Azure Functions. Basically, I have a function setup and running a basic hello world http example that looks like: module.exports = function (context, req) { context.log('JavaScript HTTP trigger function processed a request.'); context.res = { // status: 200, /* Defaults to 200 */ body: "Hello " + req.params.name }; context.done(); }; The app I am trying to deploy into a function is a simple moc client that uses swagger