WebJob is a feature of Azure App Service that enables you to run a program or script in the same context as a web app, API app or mobile app. WebJob may perform critical operations which are essential for efficient and smooth working of an app associated with WebJobs.
Serverless360 addresses pain points in managing WebJobs through Azure Portal. Once an Azure WebJob is associated to Serverless360 Composite Application, the WebJobs can be managed and monitored from a central place.
Azure WebJob is categorized into two types as:
- Continuous WebJobs
- Triggered WebJobs
It is important to understand their significance to better manage and monitor them. The following table describes the differences between continuous and triggered WebJobs.
|Starts immediately when the WebJob is created. To keep the job from ending, the program or script typically does its work inside an endless loop. If the job does end, you can restart it.||Starts only when triggered manually or on a schedule.|
|Runs on all instances that the web app runs on. You can optionally restrict the WebJob to a single instance.||Runs on a single instance that Azure selects for load balancing.|
|Supports remote debugging.||Doesn't support remote debugging.|
Now let’s look at what operations are possible on the WebJobs through Serverelss360 and how are they better than doing them in the Azure Portal.
Run a Triggered WebJob
Multiple WebJobs may be associated with a Web App to meet the business scheduling requirement.
Bulk Operation: Azure portal allows to Run a WebJobs one by one. This may become a tedious process if there are several WebJobs. Here Serverless360 offers an option to run multiple WebJobs in one click.
Start/Stop a Continuous WebJob
Bulk Operation: In case of a Continuous WebJob, the requirement would be to start/ stop multiple WebJobs at a go which is not possible in Azure Portal. Here Serverless360 offers an option to change the state of multiple Continuous WebJobs in one click.
It is possible to delete the WebJob from Serverless360 itself. The WebJob can be removed from the Azure subscription without you even logging in to the Azure portal.
The Properties option in the WebJob operation list can facilitate viewing the Azure WebJob properties as below.
Operations like Start/ Stop or Delete, that changes the state of the associated WebJobs are tracked under Governance and Audit section. It is possible to view the details like user who performed the operation in the description section. In addition to viewing the audit records, it is also possible to download that records in pdf and excel format.
User Access Policy
Restriction can be applied for performing critical operations like Start/Stop or Deleting the associated WebJob by enforcing User Access Policy in the settings section.