- 7 minutes to read

Manage Azure Web Jobs Monitoring

Take full control of your Azure Web Jobs with Nodinite. This page has two parts, Continuous Web Jobs and Triggered Web Jobs, so you can apply the right actions, thresholds, and history views for each type without direct access to the Microsoft Azure Portal.

  • ✅ Delegate management of all or individual Web Jobs to selected team members and business users
  • ✅ Reduce risk by limiting the number of people with high Azure access rights
  • ✅ Enable self-service and data access for business stakeholders
  • ✅ Perform remote actions and configure monitoring thresholds directly from Nodinite

The run History of a triggered Web Job with Download and Save all as .zip, and the Details of a continuous Web Job, animated walkthrough (7.12)
Animated walkthrough: open the History of a triggered Web Job, where each run has its own Actions menu with Download and Save all as .zip sits below the list, then the Details of a continuous Web Job.

Support and maintenance teams resolve issues quickly and securely, with fewer attack vectors and better business continuity for mission-critical services.

If you are new to the feature, start with Monitoring Web Jobs to understand the monitoring model before you use the Start, Stop, Run, History, and Edit actions.

Application Management Team IT Operations Business
Your AM team can start and stop services without IT operations involvement You maintain full oversight and control Business users get data and self-service for Web Job solutions

Features

The Nodinite Azure Monitoring Agent provides these features:

As an Administrator with access to Monitoring Agents from the Remote Administration dialog, you can further manage:

  • Add and Remove Azure subscriptions
    • Add and Remove Resource groups within each subscription
  • Enable and Disable Monitoring
  • Edit thresholds

See the global Configuration and its Add Web Jobs section for more details about configuring Nodinite and the Azure Monitoring Agent.

Category Monitoring Actions Metrics/Statistics
Web Job - Continuous ✅ Yes Start
Stop
History
Details
-
Web Job - Triggered ✅ Yes Run
History
Download output
Details
Edit
-

Continuous Web Jobs

The Category 'Continuous Web Jobs' lists each continuous Web Job found in your configured Azure Subscription by name.
Continuous Web Job Resources in a Monitor View (7.12)
This image shows a Monitor View with a list of continuous web jobs found.

For more details about Web Jobs Monitoring, see Monitoring Web Jobs. To configure them, see Continuous Web Jobs configuration.

The Continuous Web Jobs category displays Resources that show the state of the last run.

You can use the following Remote Actions for the Continuous Web Jobs Category:

  1. Start Continuous Web Job
  2. Stop Continuous Web Job
  3. View History for Continuous Web Job
  4. View details for Continuous Web Job

Continuous Web Job Remote Actions menu (7.12)
This image shows a list of Remote Actions from the dropdown menu of the Action button.

Start Continuous Web Job

To start a stopped Web Job, click the Action button and select Start in the 'Control Center' section.
Start Web Job action menu item (7.12)
Start Web Job action.

The Execute action? dialog asks you to confirm your intent to Start the selected Web Job; click Yes to proceed.
Start Web Job confirmation prompt (7.12)
Confirm intent to start selected Web Job.

You see the result of the operation, either success or failure.
Continuous Web Job started successfully (7.12)
Example of a successful start result.

Stop Continuous Web Job

To stop a running Web Job, click the Action button and select Stop in the 'Control Center' section.
Stop Web Job action menu item (7.12)
Stop Web Job action.

The Execute action? dialog asks you to confirm your intent to Stop the selected Web Job; click Yes to proceed.
Stop Web Job confirmation prompt (7.12)
Confirm intent to stop selected Web Job.

You see the result of the operation, either success or failure.
Continuous Web Job stopped successfully (7.12)
Example of a successful stop result.

History for Continuous Web Job

To view the history log output for the selected Web Job, click the Action button and select History in the 'Control Center' section.
History action for a Continuous Web Job (7.12)
The Remote Action 'History' in the 'Control Center' menu.

Details for Continuous Web Job

To see more details about your Web Job, click the Action button and select Details in the 'Control Center' section.

In the list of properties, a link opens a new browser tab to the Microsoft Azure Portal for the selected Web Job.
Continuous Web Job Details dialog (7.12)
Example dialog with details.

Right after its Web App was restarted, the continuous Web Job's Details can show Pending Restart. That is the state Azure reports.

Triggered Web Jobs

The Category 'Triggered Web Jobs' lists each triggered Web Job found in your configured Azure Subscription by name.
Triggered Web Job Resources in a Monitor View (7.12)
This image shows a Monitor View with a list of the triggered web jobs found.

For more details about Web Jobs Monitoring, see Monitoring Web Jobs. To configure global or specific thresholds, see Configuring Triggered Web Jobs.

The Triggered Web Jobs category displays Resources that show the state of the last run.

You can use the following Remote Actions for the Triggered Web Jobs Category:

  1. Run Triggered Web Job
  2. View History for Triggered Web Job
  3. View details for Triggered Web Job
  4. Edit

Triggered Web Job Remote Actions menu (7.12)
This image shows a list of Remote Actions from the dropdown menu of the Action button.

Run Triggered Web Job

To run a Web Job on demand, click the Action button and select Run in the 'Control Center' section.
Run Web Job action menu item (7.12)
Run Web Job action.

The Execute action? dialog asks you to confirm your intent to Run the selected Web Job; click Yes to proceed.
Run Web Job confirmation prompt (7.12)
Confirm intent to run selected Web Job.

You see the result of the operation, either success or failure.
Triggered Web Job ran successfully (7.12)
Example of a successful run result.

History for Triggered Web Job

To view the run history of the selected Web Job, click the Action button and select History in the 'Control Center' section.
History modal with the runs of a Triggered Web Job (7.12)
Output from Remote Action 'History': the runs with start time, Run Id, and duration, the Run button, and Save all as .zip below the list.

Download output for Triggered Web Job

To download the output of one run, click the Actions button on its row in the History modal and select Download. You get the output as a flat file (.txt).
Download output action for a Triggered Web Job run (7.12)
Example of downloading the history output as a flat file.

To download all output files in a single ZIP package, click the Save all as .zip button.

Save all as .zip button (7.12)
Example of downloading all history output as a ZIP package.

Details for Triggered Web Job

To see more details about your Web Job, click the Action button and select Details in the 'Control Center' section.

Triggered Web Job Details modal (7.12)
Example modal with details.

In the list of properties in the header, a link opens a new browser tab to the Microsoft Azure Portal for the selected Web Job.

Edit Triggered Web Job

A Triggered Web Job monitors the frequency (time of last run) and duration.

To manage the monitoring thresholds, click the Action button and select Edit in the 'Control Center' section.
Edit Triggered Web Job action menu item (7.12)
Edit action option for the triggered Web Job.

A modal opens where you set the monitoring thresholds for the frequency (time of last run) and max duration.
Edit Triggered Web Job thresholds modal (7.12)
Example of the threshold configuration dialog for triggered Web Jobs.

Last run interval time Span

Enter a timespan (format: days.hours:minutes:seconds) for the max allowed lookback period since the Web Job last ran.

  • ⚠️ Warning
  • ❌ Error

Duration

Set the time in seconds for the max allowed duration for the last run.

  • ⚠️ Warning
  • ❌ Error

These checks work like Non-Events Monitoring: Nodinite alerts you when a Web Job doesn't run as often or as fast as expected.

Next Steps