- 3 minutes to read

Monitoring Web Site in Azure

Don't let your business down! Nodinite monitors your Azure Web Sites, instantly alerting you about ageing sites and enabling you to take action—without ever needing the Azure portal.

On this page, you will:

✅ Proactively monitor the age and state of your Azure Web Sites
✅ Receive actionable alerts for ageing or non-compliant sites
✅ Automate discovery and categorization of Web Sites
✅ Empower your team with self-service and role-based access
✅ Resolve issues quickly using remote actions and detailed insights

Nodinite gives you robust monitoring options for your Azure Web Sites from one or more role-based Monitor Views. You can set monitoring thresholds, automate discovery, and use remote commands as Actions to address problems fast. For a full list of available remote actions, see the Managing Web Site page.
Web Site as Resources
This image shows a list of monitored Web Sites in a Nodinite Monitor View.

Monitoring Features

  • State EvaluationNodinite checks the state of each Web Site according to your defined policy.

    If Nodinite can't check your Web Site items' state, no one else can use them either.

  • Automatic DiscoveryNodinite Azure Agent uses the Azure Rest API to automatically discover and present Web Sites.
  • Category-based MonitoringNodinite groups monitored Resources by the concept of Categories.
  • Role-based Access – You can share access to individual items using one or more role-based Monitor Views.

State evaluation for Web Site

Nodinite presents each Web Site you monitor as a [Resource][]. For example, if you have three Web Sites, you see three Resources in Nodinite.

  • The Nodinite Resources name matches the deployed Web Site name.
  • A monitored Web Site belongs to the following 'Web Site' Categories:
    • Web Site - Web App
    • Web Site - Function App

Many other Azure-related Categories exist as well. Review the Azure Logging and Monitoring Overview.

  • The Application name uses the pattern: Subscription name/Resource Group Name

Each Resource shows a state (OK, Warning, Error, Unavailable). You can override the evaluation by configuring the Expected State option for any Nodinite [Resource][].

Web Site

For Web Site Resources, Nodinite evaluates the state as described below:

State Status Description Actions
Unavailable Resource not available
  • :Nodinite: can't evaluate the 'Web Site' due to network or security-related problems
|Review [prerequisites][]| ||Error|**Error threshold is breached**|Web Site is in the Stopped State| [Start][Azure Agent - Managing Web Site - Start]| || Warning|**Warning threshold is breached**|N/A|| ||OK|**Within user-defined thresholds**|Web Site is in the Running state| [Details][Azure Agent - Managing Web Site - Details]
[Start][Azure Agent - Managing Web Site - Start]
[Stop][Azure Agent - Managing Web Site - Stop]
[Manage Api Key][Azure Agent - Managing Web Site - Manage Api Key]| ___

Alert history for Web Site

Nodinite lets you analyze alert history for your Web Sites, so you can understand how often problems occur. If your Monitor View allows it, you can search for historical state changes for any time span, either for all your Web Sites or individually. For more details, see Add or manage Monitor View.

Search Resource history
This image shows a search for alert history for all resources in the Monitor View
This image shows alert history for the selected Web Site item

Frequently asked questions

Use the troubleshooting guide to find answers to common questions and known problems.


Next Step