Monitoring Azure Web Jobs
On this page you learn how to Monitor Azure Web Jobs using the Nodinite Azure Monitoring Agent.
This page provides monitoring options for Azure Web Jobs using Nodinite from one or more role-based Monitor Views. Nodinite monitors Azure Web Jobs' operational outcome, as specified by user-defined thresholds, either global or specific. You can manage configured Azure Web Jobs; Remote commands are available as Actions to help you swiftly address reported problems. The Remote Actions are detailed on the Managing Web Jobs page.
Here's an example Azure Web Jobs as seen in a Nodinite Monitor View.
Monitoring Features
- State Evaluation - Make sure the Web Jobs has the intended run-time state!
- Time-based - Make sure your Web Jobs run when expected.
- Duration check - Make sure your Web Jobs runs as fast as you expect.
- Last Run evaluation - monitors the outcome of runs.
Note
If Nodinite can't check the state of your Web Jobs, chances are no one else can use, or benefit from them either.
- Automatic Discovery
- Nodinite Azure agents use the Azure Rest API and offer you an automatic discovery of your Web Jobs. Sharing access to any individual Web Job is very easy from within Nodinite using Monitor Views.
- Category-based monitoring - To help you manage and monitor the different type of Web Jobs, the Resources groups by Categories.
- Web Job - Continuous
- Web Job - Triggered
- Web Site- Web App
Here's a partial list of the Nodinite Categories for Web Jobs Monitoring.
Info
With Nodinite, there are many other Azure related Categories; please review the 'Azure Logging and Monitoring Overview' page for a full feature set.
- The Application name uses physical deployment paths. This pattern guarantees uniqueness:
- %Subscription name%/%Resource group name%/%App Service name%
Here's an example of 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 is a specific Web Job that you have configured. 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 on 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. There will be one Resource for each Web Job available within Monitor Views where included.
Here's an example of 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 here.
Alert history for Web Jobs
During root cause analysis or other purposes, it might be helpful to understand how often problems with your Web Jobs happen. If your Monitor View allows it, you can search for historical state changes for the provided time-span 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 is from the Monitoring Agents administration page.
Example with monitoring for Web Jobs disabled.