Monitoring ASP.NET Applications: Tools Available in Plesk Panel

Monitoring an ASP.NET application on shared Windows hosting means answering three questions regularly: is the site up, is it healthy, and is it running out of anything? Plesk gives you part of the answer, your application gives you the rest, and an outside check tells you when visitors can't reach you. This guide shows what you can monitor yourself on Domain India Windows (Plesk) hosting and what to ask support for.

1. What you can and can't see on shared hosting

On a shared Windows server, many customers' sites run side by side. Plesk shows each customer the tools for their own subscription and keeps server-wide tools for the administrator.

Menu names differ slightly between Plesk versions and with your plan's settings. If a tool mentioned here is missing, use the search box at the top of Plesk, or ask support.

2. Read your logs

Logs are the most useful monitoring tool you have. In Plesk, open Websites & Domains, pick your domain and choose Logs. You can filter by type and date, and the raw files sit in the logs folder of your subscription for download.

Check them on a schedule, not only when something breaks. A weekly look is enough for most sites. Watch for:

• A rising number of 500 errors, which point to a bug or a failing dependency.
• 503 errors, which usually mean your application pool stopped.
• Slow pages, visible in the time-taken column of the IIS access log.
• Many failed logins from a few addresses, which suggest password guessing.

The full guide to reading IIS log lines, including the UTC timestamps, is in checking Plesk logs.

3. Track disk space and traffic

Your plan has a storage allowance and, on ASP Starter and ASP Business, a monthly bandwidth allowance. Open Statistics in Plesk to see how much of each your subscription has used.

Things that quietly eat disk space on a Windows site:

• log files, including an ASP.NET Core stdout log left switched on;
• backups stored inside your subscription rather than downloaded;
• uploaded files your application never cleans up;
• old copies of your published site left in folders next to httpdocs.

If you are close to a limit, clean up first, then consider a larger plan. Plan sizes are in Windows hosting plans comparison.

4. Add a health-check page to your app

Plesk can't tell whether your application is working, only whether requests are answered. A health-check page lets you, and any monitor, test the parts that matter, such as the database connection.

In ASP.NET Core, the built-in health checks take a few lines in Program.cs:

builder.Services.AddHealthChecks();

var app = builder.Build();
app.MapHealthChecks("/health");

The page returns Healthy with status 200 when all checks pass. You can add a database check with a health-check package for SQL Server, so a broken connection string shows up as Unhealthy rather than as a confusing error on the home page.

On .NET Framework, a simple page or handler that opens a database connection and returns "OK" does the same job.

5. Log from inside your application

Server logs tell you that a request failed. Your application's own log tells you why. Use the logging built into your framework:

• ASP.NET Core: ILogger with a file or database sink. Log exceptions with the request path and a timestamp.
• .NET Framework: a logging library, or Application_Error in Global.asax writing unhandled exceptions to a file.

Write log files into a folder your application pool is allowed to write to, such as App_Data, never into httpdocs where visitors could download them. If writing fails with "access denied", see managing ASP.NET file permissions in Plesk. Rotate or delete old log files so they don't fill your disk.

6. Watch uptime from the outside

Nothing inside the server can warn you when the server, the network or your domain's DNS is the problem. An external uptime monitor can. Many services offer a free tier that requests a URL every few minutes and emails you when it fails.

Some monitors also warn you before your SSL certificate expires. Plesk renews free Let's Encrypt certificates automatically, but a warning still helps if renewal fails because the domain stopped pointing at your hosting.

7. When to contact support

Contact support if your monitor shows the site down and your logs show nothing at that time, if every site on your subscription fails at once, or if you need something from the server's own logs. Include your domain, the exact time with time zone, and what your monitor or logs showed.

Domain India support is on 24/7 live chat, and tickets get a first response within 15 minutes; how long a fix takes depends on the issue. There is no phone support.

8. Where Domain India fits

Windows hosting at Domain India is for ASP.NET, classic ASP and MSSQL applications managed through Plesk. The plans differ in sites, storage, bandwidth and databases, and ASP Enterprise lists a dedicated application pool, which keeps other customers' traffic from restarting your app. The live card shows today's price, excluding 18% GST.

For the rest of the panel, read the Plesk Windows hosting guide.

Ready to keep an eye on your site? Open My Hosting and click the Plesk button to check your logs, compare the Windows hosting plans, or open a ticket if something looks wrong.