Monitoring Azure Web Jobs
Gain complete visibility and control over your Azure Web Jobs with Nodinite. This page guides you to monitor, evaluate, and manage Web Jobs efficiently—so your teams act before issues impact your business.
With this feature, you will:
✅ Proactively monitor and receive real-time alerts for all Azure Web Jobs
✅ Control everything centrally—no need for direct Azure portal access
✅ Automate state evaluation and enforce policies
✅ Enable role-based access and self-service for your teams
✅ Reduce risk and human error with secure, delegated access
Learn how to monitor Azure Web Jobs using the Nodinite Azure Monitoring Agent.
Nodinite provides monitoring options for Azure Web Jobs from one or more role-based Monitor Views. You monitor the operational outcome of Azure Web Jobs using user-defined thresholds—globally or specifically. Manage your configured Azure Web Jobs and use Remote Actions to resolve issues quickly. For more on remote management, see Managing Web Jobs.
This image shows Azure Web Jobs in a Nodinite Monitor View.
Monitoring Features
- State Evaluation — Instantly see if your Web Jobs have the intended run-time state.
- Time-based — Ensure your Web Jobs run when you expect.
- Duration check — Ensure your Web Jobs run as fast as you expect.
- Last Run evaluation — Monitor the outcome of runs.
Note
If Nodinite can't check the state of your Web Jobs, no one else can use or benefit from them either.
- Automatic Discovery — Nodinite Azure agents use the Azure REST API to automatically discover your Web Jobs. You can easily share access to any individual Web Job from within Nodinite using Monitor Views.
- Category-based Monitoring — Organize and monitor different types of Web Jobs by Categories.
- Web Job - Continuous
- Web Job - Triggered
- Web Site- Web App
This image shows a partial list of the Nodinite Categories for Web Jobs Monitoring.
Info
With Nodinite, you can monitor many other Azure-related Categories. Review the 'Azure Logging and Monitoring Overview' page for a full feature set.
- The Application name uses physical deployment paths for uniqueness:
- %Subscription name%/%Resource group name%/%App Service name%
This image shows the Application naming pattern for Azure Web Jobs Resources.
- %Subscription name%/%Resource group name%/%App Service name%
Continuous Web Job
Each Continous Web Job in Azure maps to a Nodinite Resource. It can have any of the following states:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Continous Web Job' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | There is at least one problem |
|
Start History Details | |
| OK | Web Job is operational |
|
Stop History Details |
A common use case: You configure a Web Job, and then someone accidentally removes it (for example, your DevOps-based automatic deployment fails to redeploy a business-critical Web Job).
Web Job example when not available.
From within Nodinite, you can reconfigure the state evaluation at the Resource level using the Expected State feature.
Triggered Web Job
Each Triggered Web Job in Azure maps to a Nodinite Resource. It can have any of the following states:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Resource not available | Evaluation of the 'Web Job' is not possible either due to network or security-related problems | Review prerequisites | |
| Error | Error threshold is breached |
|
Run History Details Edit | |
| Warning | Warning threshold is breached |
|
Run History Details Edit | |
| OK | Within user-defined thresholds |
|
Run History Details Edit |
As an example, the Nodinite Azure Web Jobs Logging and Monitoring agent evaluates the outcome of the last run of Web Jobs. You get one Resource for each Web Job available within Monitor Views where included.
This image shows state evaluation where the last Run succeeded for a Triggered Web job as seen in a Nodinite Monitor View.
Web App Web Site
This Monitoring feature is documented in detail on the Azure Web App Monitoring page.
Alert history for Web Jobs
During root cause analysis, you can review how often problems with your Web Jobs happen. If your Monitor View allows it, you can search for historical state changes for all your Web Jobs or individually. This topic is detailed within the generic instructions on how to Add or manage Monitor View page.
| Search | Resource history - Continous | Resource history - Triggered |
|---|---|---|
 Search for alert history for all Resources in the Monitor View |
 Alert history for the selected Continous Web Job. |
 Alert history for the selected Triggered Web Job. |
Frequently asked questions
You can find solutions to common problems and the FAQ in the troubleshooting guide.
How do I enable the monitoring of Web Jobs?
To monitor Web Jobs, configure the Agent with the Enable monitoring checkbox (checked by default). The details are available in the 'Configuration' user guide.
The screenshot from the remote configuration form comes from the Monitoring Agents administration page.
Example with monitoring for Web Jobs disabled.