- 6 minutes to read

Monitoring Azure Web Jobs

Gain complete visibility and control over your Azure Web Jobs with Nodinite. This page shows how you 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, with 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

The Web Jobs of a Web App in a Monitor View, the run History of a triggered Web Job, and the Details of a continuous Web Job, animated walkthrough (7.12)
Animated walkthrough: the Web Jobs of a Web App in a Monitor View, the run History of a triggered Web Job, the Details of a continuous Web Job with the state Azure reports, and its Resource back in the Monitor View.

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, set globally or specifically, and get alerts through Alarm Plugins. Manage your configured Azure Web Jobs and use Remote Actions to resolve issues quickly; see Managing Web Jobs.
Web Jobs as Resources in a Monitor View (7.12)
This image shows Azure Web Jobs in a Nodinite Monitor View.

graph LR WJ["fa:fa-business-time Azure Web Jobs
Continuous and Triggered"] -->|"Azure REST API"| AG["fa:fa-monitor-waveform Azure Monitoring Agent"] AG --> OK["fa:fa-check OK
Running, last run successful"] AG --> WA["fa:fa-triangle-exclamation Warning
Too seldom or too long"] AG --> ER["fa:fa-xmark Error
Stopped, failed, or Error threshold"] AG --> UN["fa:fa-ban Unavailable
Removed or no access"] WA --> AP["fa:fa-bell Alarm Plugins"] ER --> AP ER --> RA["fa:fa-bolt Remote Actions"] style OK fill:#93d16d style WA fill:#f0955a style ER fill:#c33d34,color:#fff style UN fill:#eeeeee style AG fill:#2678BD,color:#fff

Diagram: The agent evaluates each Web Job Resource into OK (green), Warning (orange), Error (red), or Unavailable (light grey); Warning (Triggered Web Jobs only) and Error raise alerts, and you resolve problems with Remote Actions.

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, in the spirit of Non-Events Monitoring.
    • 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 discover your Web Jobs automatically. Share access to any individual Web Job with Users through Monitor Views.
  • Category-based Monitoring — Organize and monitor different types of Web Jobs by Categories.

Web Job Categories (7.12)
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%

Application path example for Azure Web Jobs (7.12)
This image shows the Application naming pattern for Azure Web Jobs Resources.

The Monitoring Service collects the evaluated state from the agent.

Continuous Web Job

Each Continuous 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 'Continuous Web Job' is not possible either due to network or security-related problems Review prerequisites and the firewall settings
❌ Error There is at least one problem
  • Web Job is in the stopped state (Log Text Stopped)
  • Last run failed
Start
History
Details
✅ OK Web Job is operational
  • Web Job is enabled
  • Last Run is successful
  • The Log Text is empty
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 Resource in the Unavailable state (7.12)
A Web Job that is not available: its row is light grey, with the Log Text "This specifically monitored Web Job was not found in the list of …".

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
  • Web Job is in the stopped state
  • Last run failed
  • Run has not executed within the Error threshold
  • Run duration above the error threshold
Run
History
Download output
Details
Edit
⚠️ Warning Warning threshold is breached
  • Run has not executed within the Warning threshold
  • Run duration is above the Warning threshold
Run
History
Download output
Details
Edit
✅ OK Within user-defined thresholds
  • Web Job is enabled
  • Last Run is successful
Run
History
Download output
Details
Edit

Set the thresholds globally or per Web Job in the Triggered Web Jobs configuration, or with the Edit Remote Action.

As an example, the Nodinite Azure Monitoring Agent evaluates the outcome of the last run of Web Jobs. You get one Resource for each Web Job, available within the Monitor Views that include it.

Triggered Web Job last run state as Resources (7.12)
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

The Monitoring Web Site page documents this Monitoring feature in detail; for its Remote Actions, see Managing Web Site.


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. The generic Add or manage Monitor View page describes this in detail.

Search Resource history - Continuous Resource history - Triggered
Search for alert history (7.12)
Search for alert history for all Resources in the Monitor View
Alert history for the selected Continuous Web Job (7.12)
Alert history for the selected Continuous Web Job.
Alert history for the selected Triggered Web Job (7.12)
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, for example The Web Jobs are not listed as Resources.

How do I enable the monitoring of Web Jobs?

To monitor Web Jobs, check Enable monitoring of triggered Web Jobs on the tab Web Jobs - Triggered, and the matching checkbox on the tab Web Jobs - Continuous (both checked by default). The tabs are on the subscription card under Monitoring in the Remote Configuration. You must also include the Resource Groups that host the Web Jobs. The Add Web Jobs section of the Configuration guide has the details.

The screenshot from the Remote Configuration form comes from the Monitoring Agents administration page.
Remote Configuration, tab Web Jobs - Triggered, with Enable monitoring of triggered Web Jobs cleared (7.12)
The tab Web Jobs - Triggered with Enable monitoring of triggered Web Jobs cleared.

Next Steps