Web App
  • 05 Aug 2026
  • 5 Minutes to read
  • Dark
    Light
  • Download PDF

Web App

  • Dark
    Light
  • Download PDF

Article summary

Overview

Web App is a Microsoft-developed and managed cloud computing platform for hosting websites — a platform as a service (PaaS) that publishes web apps running on multiple frameworks and written in various programming languages.

Business value

Managing Web App status from Turbo360 lets you respond to availability and performance issues across multiple apps without switching to the Azure portal, reducing the time to detect and resolve hosting issues.

How it works

Once a Web App is associated with a Business Application, its status, dashboard, and monitoring become directly manageable from Turbo360, and any operation performed is reflected in the Azure portal.

Permissions

Access to Web App actions is controlled through RBAC when adding a role to a Business Application.

PermissionDescription
ReadView dashboard and monitoring configuration.
ManageStart, Stop, and Restart the app, and configure monitoring rules.

Operations

Turbo360 lets you control Web App status directly, without switching to the Azure portal.

Start, Stop, and Restart

  • Start — bring a stopped Web App online.
  • Stop — shut down a running Web App.
  • Restart — stop and start the app in sequence.

Web app operations.png

Bulk operations

  • Bulk Start/Stop/Restart — perform the same operation on multiple selected Web Apps from the Web App resource section. Use this when several apps need the same status change together, such as during planned maintenance.

Bulk.png

Resource dashboard

The dashboard surfaces request, error, and resource signals so you can spot host-level performance issues without leaving Turbo360.

WidgetWhat it shows
Data In CountVolume of inbound data to the app.
Requests CountVolume of incoming requests to the app.
Http ErrorsCount of HTTP errors returned by the app.
Data In vs Data OutCompares inbound data volume against outbound data volume.
Garbage CollectionsCount of garbage collection events, useful for spotting memory pressure.
IO Read vs IO WriteCompares disk read volume against write volume.

webapp 3.JPG

Metrics

The Metrics tab surfaces request volume, error rate, and resource consumption data for Web App, giving you visibility into application performance trends over time. Use the Metrics tab to correlate HTTP error spikes or response time increases with deployment events or traffic surges, and to confirm that performance returns to baseline after restarts or scaling operations.

You can add, remove, or reconfigure widgets to focus on the metrics most relevant to your support scenario.

Monitoring

Web App supports Status, Instance, Quotas, and Metric monitoring rules, configured under the resource's Monitoring section, with metric-type rules allowing selection of specific metrics.

webapp4.gif

State monitoring

Tracks whether the Web App is in the running state. Use this when you need to be alerted if the app is not in the expected state; an auto-correct feature can have Turbo360 turn the app back on automatically.

  1. Navigate to the Monitoring section of the resource.
  2. Configure the state rule with the desired threshold.
  3. Click Save.

Metric monitoring

Tracks Web App performance metrics, which vary depending on the application's behavior and usage patterns.

  1. Navigate to the Monitoring section of the resource.
  2. Select the necessary monitoring metrics and configure the threshold values.
  3. Click Save.

Monitoring recommendations

State Monitoring

State monitoring raises an alert if your application is not in the expected state. In the example below, monitoring is configured to raise an alert if the Web App is not in the running state.

webapp 5.JPG

There is also an auto-correct feature where you can tell Turbo360 to turn the web app back on if it is not running.

Metrics Monitoring

The metrics monitoring for your application will often vary depending on what your application does and its typical usage patterns. Some common scenarios are below:

MetricWarningError
Http Server Errors> 20> 50
Response Time25
Average Memory working setVariesVaries
  • You might decide to tune the HTTP 400 range of response codes depending on the individual usage of your application.
  • Response Time is the time taken in seconds for your application to respond. This is common across all pages or APIs in this application — a good way to check on the overall response SLA, and you would choose a value that meets your SLA.
  • HTTP Server Errors is the number of 500 range responses returned by your application.
  • Average Memory working set is a common counter to monitor based on the expected memory use of your application. The thresholds vary depending on what your application does and the size of the plan you are using.
  • You may also choose to monitor metrics on a case-by-case basis.

Consider your App Service Plan

When considering the monitoring for your web app, also consider the App Service Plan. If you have multiple apps on the same plan, resources are shared across all of the apps.

Default Settings

In the Turbo360 monitoring profiles feature, you can configure standard default settings for this resource type, which can be applied to resources you add to a Business Application to reduce the maintenance of monitoring configuration.

Application Insights

If you want to do some lower-level monitoring below the metrics API, you can use Application Insights with your web app — add Application Insights to your Business Application, where Kusto queries can be used to provide lower-level monitoring if you want to monitor specific routes or dependencies.

See Application Insight for more detail.

API EndPoint Monitor

Turbo360 has an API Endpoint monitor feature that can ping your API endpoint to add monitoring of the response for specific endpoints if you want to test them from the outside.

See API Endpoint monitoring for more detail.

More Info

If you want to learn more about some of the lower-level considerations for monitoring Web Apps, Microsoft documents the counters on this page:

Microsoft's Web App monitoring documentation

Troubleshooting

  1. Start, Stop, or Restart operation fails
    Cause: The app is in a transitional state, or the role lacks the Manage permission.
    Fix: Wait for the current state transition to complete, or confirm the role has Manage access, then retry.
  2. State monitoring rule does not auto-correct
    Cause: No auto-correct status was configured on the rule.
    Fix: Edit the rule and specify an auto-correct status.
  3. Metric monitoring rule fires unexpectedly
    Cause: The threshold reflects aggregate performance across all apps sharing the same App Service Plan.
    Fix: Review the threshold in light of the shared plan, and adjust to account for combined load.
  4. Dashboard widgets show no data
    Cause: The app was recently associated and has not completed its first monitoring cycle.
    Fix: Wait for the next monitoring cycle, then refresh the dashboard.

Was this article helpful?

What's Next