Server Diagnostics — professional server monitoring and diagnostics inside Webasyst

Server Diagnostics is a Webasyst application that helps administrators, website owners, or online store owners monitor the state of their server directly from the control panel.

The application displays CPU load, memory usage, disk status, inode usage, network connections, PHP environment, database, cron tasks, system limits, SSL certificates, security HTTP headers, and other important parameters.

The main goal of the application is to help you spot problems in advance — before the site starts slowing down, stops loading, or users begin contacting support.

Server control without constant SSH connections

You no longer need to connect via SSH, open the console, and manually run commands every time you want to check the server status.

Key metrics are available directly in Webasyst: load, memory, disk, inode, processes, PHP, database, network, SSL, and security check results.

This is convenient for website owners, developers, technical support teams, and administrators who need to quickly understand what is happening with the server.

Why it matters

Many server issues become visible too late:

• disk space is running out;
• inodes are exhausted;
• the server is overloaded by CPU;
• there is not enough RAM;
• errors accumulate in logs;
• cron tasks are not running;
• the certificate is about to expire or does not cover the required domain;
• important security HTTP headers are missing;
• sensitive files are exposed;
• suspicious configuration changes appear.

When such problems are discovered only after customer complaints, the site may be unavailable, slow, or lose orders.

It's better to see problems in advance

The application helps detect typical risks before a critical failure occurs: increasing load, disk filling, inode shortage, cron errors, SSL issues, missing security headers, and exposure of sensitive files.

This is especially useful for online stores, where site downtime can lead to lost orders and customer support requests.

How the application works

1. Collects system data — CPU, RAM, disk, inode, processes, network, PHP, database, and system limits.
2. Performs security checks — sensitive files, HTTP headers, SSL certificates, open ports, and basic configuration risks.
3. Saves metrics history — data can be analyzed over time, not just viewed in the current state.
4. Displays charts and summaries — load and key indicators are available in a convenient Webasyst interface.
5. Sends notifications — when thresholds are exceeded or problems are detected, the application can notify you via Email, Telegram, or Webhook.

Main features

• CPU monitoring — current load and history.
• RAM monitoring — RAM usage.
• Disk control — free space, used space, and usage percentage.
• Inode control — important metric for hostings and servers with a large number of files.
• Server processes — overview of active processes and load.
• Load charts — metric history in a convenient format.
• PHP environment — PHP version, limits, extensions, and important parameters.
• Database — basic information about connection and status.
• Cron tasks — control of background processes and automatic metric collection.
• System logs — viewing and analyzing available logs.
• System limits — FD, file-max, RLIMIT, and other parameters.
• Kernel parameters — safe subset of sysctl.
• System entropy — control of entropy_avail.
• Container and hosting limits — cgroup CPU/RAM if the server runs in a containerized environment.
• Diagnostics export — export data to JSON for analysis or support.

All important metrics on one screen

Instead of manually checking different console commands, the application gathers the main data in one interface.

You can understand faster what is happening with the server: where resources are lacking, which checks need attention, and which parameters may affect site stability.

Network and SSL diagnostics

• TCP connection summary: ESTABLISHED, TIME_WAIT, LISTEN, and other states;
• Network traffic monitoring RX/TX;
• Security HTTP headers check by domains;
• HSTS check;
• CSP check;
• X-Frame-Options check;
• X-Content-Type-Options check;
• Referrer-Policy check;
• Permissions-Policy check;
• SSL certificate check;
• Certificate expiration control;
• SAN and domain coverage check;
• Let's Encrypt wildcard diagnostics;
• Caching of heavy check results;
• Manual full checks from the interface.

SSL is checked beyond just the presence of a certificate

The application helps you understand whether the certificate covers a specific domain, which names are listed in SAN, and when the certificate expires.

This is especially important when using wildcard certificates, multiple domains, subdomains, and proxying through different servers.

Website security monitoring

The application performs a set of safe checks that help detect typical configuration errors and potential risks.

• Check access to sensitive files;
• Search for open backup files;
• Search for open dump files;
• File system permissions control;
• Open ports analysis;
• Basic server configuration check;
• Detection of potentially dangerous settings;
• Safe diagnostics mode with a minimum number of shell commands.

Safe diagnostics mode

On restricted hostings, not all system commands may be available. Therefore, the application uses careful fallback mechanisms and shows only the data that can be safely obtained in the current environment.

If the hosting prohibits some checks, the application will continue to work and show the available diagnostics.

Problem notifications

Server Diagnostics can automatically notify you about critical situations so the administrator learns about the problem before the users do.

• Email notifications;
• Telegram notifications;
• Webhook events for integrations;
• Customizable CPU thresholds;
• Customizable RAM thresholds;
• Customizable disk thresholds;
• Notification pause to protect against spam;
• Email sending test;
• Telegram sending test;
• Log of sent notifications and incidents.

Notifications help you not miss a critical moment

If the disk is almost full, the load is too high, or memory is running out, the application can send a notification to the administrator.

You can configure thresholds and the pause between notifications to receive important messages without unnecessary spam.

Server change control — baseline

Baseline helps save a reference state of the server and then compare it with the current state.

• Saving a reference system state;
• Detection of configuration changes;
• Server snapshot history;
• Root cause analysis after updates;
• Incident log;
• Threshold exceedance log.

This is convenient after updates, site migrations, PHP version changes, server configuration, or installation of new modules.

Automatic metrics collection via CRON

To automatically collect load history, build charts, and perform regular server checks, you can set up a standard Webasyst CLI task.

Example CRON command:

*/10 * * * * /usr/bin/php /path/to/webasyst/cli.php serverinfo metrics

Where /path/to/webasyst/ is the path to the root folder of the installed Webasyst.

The launch interval can be changed for your server. For example:

• */5 * * * * — every 5 minutes;
• */10 * * * * — every 10 minutes;
• */30 * * * * — every 30 minutes;
• 0 * * * * — once per hour.

Important note about CRON

Automatic metric collection uses the standard Webasyst CLI mechanism via the cli.php file.

If you don't know the path to PHP or the Webasyst root folder, you can check it in your hosting panel or with your server administrator.

Operation on shared hosting

The application can work not only on VPS or dedicated servers but also on many shared hostings.

• Safe diagnostics mode;
• Minimum shell commands;
• Fallback mechanisms for restricted environments;
• Display of available data without critical errors;
• Correct operation even when some system functions are prohibited.

On shared hosting, some system information may be unavailable due to provider restrictions. In this case, the application will show the data that is allowed to be retrieved in the current environment.

Supported environments

• Webasyst;
• Linux servers;
• VPS/VDS;
• Dedicated servers;
• Shared hostings with Webasyst support;
• Containerized environments (if required system data is available).

The application performs best on VPS/VDS or dedicated servers, where more system information is available.

What you can monitor

• CPU load;
• RAM usage;
• Free disk space;
• Inodes;
• Network connections;
• RX/TX traffic;
• Active processes;
• PHP status;
• Database parameters;
• Cron tasks;
• System limits;
• Access to sensitive files;
• Security HTTP headers;
• SSL certificates;
• Configuration changes;
• Incident history.

Who the application is for

• Online stores on Webasyst;
• Website owners;
• Server administrators;
• Webasyst developers;
• Technical support teams;
• DevOps specialists;
• Agencies that maintain client websites;
• Projects where it is important to quickly see the technical state of the server.

Advantages of Server Diagnostics

• Works directly inside Webasyst;
• Does not require third-party cloud services;
• Does not send data to third parties;
• Shows server status in one interface;
• Helps find the causes of problems faster;
• Suitable for daily site monitoring;
• Supports metrics history;
• Shows load charts;
• Checks SSL and security headers;
• Can send notifications;
• Helps prevent failures;
• Simplifies technical support work.

Server Diagnostics vs external monitoring systems

For most websites and online stores, the capabilities of the application are sufficient for daily server health monitoring. For complex infrastructures, Server Diagnostics can be used together with external monitoring systems.

What you get in the end

• Quick overview of server status;
• Early problem detection;
• Control of load and resources;
• Metrics history and charts;
• Website security checks;
• SSL certificate control;
• Security HTTP headers check;
• Notifications about critical situations;
• Convenient tool for support and diagnostics.

Setup steps

1. Install the application in Webasyst.
2. Open the Server Diagnostics section.
3. Check which system data is available on your hosting or server.
4. Set up notification thresholds for CPU, RAM, and disk.
5. If needed, connect Email, Telegram, or Webhook notifications.
6. Set up CRON via the standard Webasyst CLI mechanism.
7. Verify metrics history collection and charts.
8. Run full security and SSL checks.
9. Save a baseline if you want to control configuration changes.

Requirements

• Installed Webasyst;
• Linux hosting, VPS/VDS, or dedicated server;
• Access to CRON configuration (if you need metrics history and automatic data collection);
• Available PHP functions and system utilities for advanced checks;
• Email, Telegram, or Webhook (if notifications are needed).

Limitations

Availability of some data depends on the server or hosting

Some checks depend on user permissions, PHP settings, hosting security policy, and the availability of system utilities.

On VPS/VDS and dedicated servers, more diagnostic information is usually available. On shared hostings, some checks may be unavailable, but the application will continue to show the accessible data.

Frequently Asked Questions

Do I need to constantly connect to the server via SSH?
No. For daily server status checks, SSH is not required — the main metrics are available directly in Webasyst.

Is CRON required?
For one-time viewing of the current state — no. For automatic history collection, charts, and regular checks, it is recommended to set up CRON via the standard Webasyst CLI mechanism.

What is the correct CRON command?
Use the command via cli.php:

*/10 * * * * /usr/bin/php /path/to/webasyst/cli.php serverinfo metrics

Is the application suitable for shared hosting?
Yes, but the set of available data depends on the hosting limitations. If some system functions are prohibited, the application will show the available information and will not require unavailable checks.

Are data sent to third-party services?
No. Diagnostics works inside your Webasyst. Notifications are sent only to the channels you configure yourself: Email, Telegram, or Webhook.

Is this a replacement for external monitoring?
For most websites and online stores, the application covers the main tasks of daily control. For complex infrastructures, it can be used in conjunction with external monitoring systems.

Can I export diagnostics?
Yes. Diagnostic data can be exported to JSON for analysis, support, or transfer to an administrator.

Summary

Server Diagnostics turns Webasyst into a convenient server health control center.

The application helps you monitor load, memory, disk, inode, network, PHP, database, SSL, security HTTP headers, sensitive files, system limits, and metrics history.

This is a useful tool for website owners, online stores, developers, and administrators who want to quickly spot problems and maintain stable operation of their project.

Like the application? I'd appreciate your review and feedback!

If Server Diagnostics helped you find a problem faster, set up server monitoring, or improve site stability — please leave a review in the Webasyst store.

Your reviews, ideas, and suggestions help develop the application, add new checks, and make the tool more convenient for website owners and administrators.

I'm always available and happy to help. If you have any questions about setup, usage, or would like to suggest improvements — write to me on Telegram or by email.

Telegram: t.me/+Zk3IiWq_pDRiN2Uy
Email: developer@misiuk.ru

For a faster response, it's better to write on Telegram. If email is more convenient — I will definitely reply.

Thank you for choosing Server Diagnostics!