In the field of Measurements your CURIAWEB cPanel, you can find statistics, logs, and diagnostic information for your websites and hosting account. Here, for example, you can analyze website traffic, view web server error messages, monitor the transferred data volume, and check your account's resource consumption.
At CURIAWEB you will find the functions in this area Visitors, Error, bandwidth, raw access data, AWStats, Webalizer, Webalizer FTP, Measurement data editor and Resource usage.
In this article, we explain what information these tools provide and which one you should use for a specific task.
Briefly explained: The area Measurements helps you with two different tasks: you can statistically evaluate the use of your website and investigate technical problems. For troubleshooting, in particular Error and Resource usage Important.
Where do you find the measured values? #
Log in to your CURIAWEB cPanel and open the section on the home page Measurements.
There you will find the following features:
- Visitors
- Error
- bandwidth
- raw access data
- AWStats
- Webalizer
- Webalizer FTP
- Measurement data editor
- Resource usage
An overview of all areas of your cPanel can be found under cPanel at CURIAWEB explained: All areas and functions at a glance.
Visitors #
The function Visitors shows information about the recent accesses to your website. Data from the web server logs is evaluated in the process.
Depending on the existing log entry, you can tell there, for example, which resource was called, which IP address the request came from, when it took place, and what HTTP status the web server returned.
Therefore, the tool is not only interesting for a quick overview of accesses. It can also help with troubleshooting.
What can you use visitors for? #
Assuming that a specific page on your website is supposed to have been accessed and you want to check whether the request actually reached the web server, the latest access logs can provide an initial indication.
Even unusual or repeated requests from certain clients can become visible in the access data.
Important: The function Visitors is not a complete web analysis like a specialized analytics solution, for example. It shows technical access information from the server logs and serves a different purpose.
HTTP status codes in the access logs #
When analyzing access logs, you may encounter various HTTP status codes. They show how the web server processed a request.
Some common examples are:
200- Request was successfully processed301- permanent redirect302– temporary redirect403– Access denied404– requested resource was not found500- Internal Server Error503– Service temporarily unavailable
However, a single status code does not always explain the complete cause of a problem. Rather, it is a starting point for further diagnosis.
Error #
Under Error does cPanel show current entries from the web server error log?.
This function is particularly important when a website shows a technical error, a PHP application does not run correctly, or the web server cannot process a request as expected.
An error log can, for example, contain indications of a problematic file, a faulty configuration, or other technical causes.
Practical Tip: If a website shows a reproducible error, reload the problematic page and then promptly check the error log. A new entry with a matching timestamp makes it easier to associate it with the specific error.
Why is the timestamp important? #
An error log can contain numerous entries. Not every one of them belongs to the problem you are currently investigating.
If the error, for example, by 10:32 time occurred, entries from the same period are significantly more interesting than reports from an earlier time.
During troubleshooting, you should therefore always record as precisely as possible when the error occurred and which URL or action triggered it.
Not every report is automatically critical #
In addition to serious errors, logs can also contain warnings or other technical notes. An existing log entry therefore does not automatically mean that this exact message caused your website to crash.
Factors include the time, the affected file, the type of message, and the context of the observed problem.
We will cover how to systematically evaluate such entries later under Read cPanel Error Log and find website errors.
bandwidth #
The function bandwidth shows you how much data was transferred in connection with your hosting account.
For example, when a visitor accesses a website, HTML files, images, stylesheets, JavaScript files, and other resources must be transferred from the server. Other services can also generate traffic.
The bandwidth indicator helps you monitor the development of this data traffic.
Bandwidth is not the same as storage space #
These two terms are often confused.
Storage space describes how much data is stored on your hosting.
bandwidth or data transmission on the other hand, describes the amount of data transferred between your hosting and other systems.
For example, a website may take up only a few gigabytes of storage space, but transfer significantly larger amounts of data due to many views.
Briefly explained: Storage space answers the question „How much data is on my hosting?“. Bandwidth answers the question „How much data was transferred?“.
We will show you how to check both values later at Check disk space and bandwidth in cPanel.
raw access data #
With raw access data Can you use or download the raw access logs of your website, provided the relevant data is available.
Unlike graphically prepared statistics, here you receive the actual log data, on the basis of which various evaluations can be created.
Such raw data are particularly interesting for technical analyses when summarized statistics do not provide sufficient information.
What is in an access log? #
A web server logs various technical information during a request. This can include, among other things, the timestamp, requested resource, HTTP method, status code, amount of data transferred, and information about the requesting client.
What exact information is available depends on the log format used and the server configuration.
For large websites, such logs can become very large. For normal visitor statistics, tools like AWStats are therefore much more convenient.
Privacy Policy: Server logs can contain technical information such as IP addresses. Therefore, do not treat exported log files like arbitrary public files and do not make them available unprotected on the web.
AWStats #
AWStats analyzes web server logs and compiles statistics on website usage from them.
The evaluations may contain information on accesses, pages viewed, data volumes transferred, time periods, and various technical characteristics of the requests, among other things.
AWStats operates fundamentally differently from browser-based analytics systems that, for example, integrate JavaScript into a website.
What does „Unique visitors“ mean? #
AWStats can aggregate traffic into estimated unique visitors. However, such values must not be equated with an exact number of real people.
Server log analysis must distinguish visitors based on technical characteristics. For example, multiple people may use the same public IP address, while a single person may appear multiple times under different technical conditions.
The value is therefore suitable for statistical orientation, but is not an exact head count.
What is a visit? #
A Visit tries to group related requests into a session or visit.
This value is also based on the statistical program's evaluation method and should not be confused with an exactly identified person.
What are pages and hits? #
Also Pages and Hits do not mean the same thing.
A requested webpage can consist of numerous individual resources. In addition to the actual HTML document, things like images, stylesheets, scripts, and other files are requested, for example.
Therefore, a single page view can generate multiple server requests.
Important: A high number of hits does not automatically mean that the exact same number of pages were viewed by real visitors. For a meaningful interpretation, you need to understand which metric you are currently looking at.
Why don't AWStats and other analytics systems match up exactly? #
Different statistical systems use different data sources and measurement methods.
AWStats analyzes server logs. Other analysis tools, on the other hand, can, for example, use JavaScript in the browser and only register a visit when this script is actually executed.
Additionally, bots, caching, privacy mechanisms, blocked scripts, and varying definitions of a session can influence the values.
Discrepancies between two statistical systems are therefore fundamentally possible and do not automatically indicate an error.
Bots and crawlers in website statistics #
Not every access to a publicly accessible website comes from a human.
Search engine crawlers, monitoring systems, security services, and numerous automated bots also access websites.
Server-side logs generally record such requests as well. Statistical programs sometimes attempt to separately detect and report known bots, but a perfect classification of all automated traffic is not possible.
Practical Tip: Therefore, do not interpret server-based visitor numbers in isolation. For example, an unusual increase in traffic can also be caused by bots or automated requests.
Webalizer #
Webalizer is another tool for the statistical analysis of web server access.
Similar to AWStats, Webalizer processes existing log data and generates clearer statistics from it.
The presentation and calculation of individual metrics differ between the programs. Therefore, values from AWStats and Webalizer do not have to be exactly identical.
For normal operation, you do not need to evaluate both systems in parallel. If you want to compare long-term developments, it makes sense to use the same data source and the same metrics as consistently as possible.
Webalizer FTP #
Webalizer FTP is intended for statistical information on FTP access.
While Webalizer analyzes accesses to web content, Webalizer FTP refers to corresponding file transfers via FTP.
For most website operators, this statistic is less important in everyday life. However, it can be helpful for special investigations into FTP traffic.
Measurement data editor #
With the Measurement data editor you can select—as far as supported by the server configuration—which available statistics programs should be used for your domains.
Which options are actually displayed there depends on the statistical functions provided on the server.
You usually do not need to change these settings if the desired statistics are already available.
Resource usage #
The function Resource usage belongs to the most important diagnostic tools of your CURIAWEB web hosting.
CURIAWEB uses a CloudLinux hosting environment. CloudLinux makes it possible to manage the resources of an individual hosting account in a controlled manner and to monitor their usage.
This allows you to see whether your website is heavily utilizing certain resources or temporarily reaching a limit that applies to your account.
Which resources can be displayed? #
Depending on the view and server configuration, you may encounter different metrics. These include, for example:
- CPU
- RAM
- I/O
- IOPS
- Entry Processes
- Processes or NPROC
These values measure different resources. An achieved limit should therefore not be interpreted broadly as „too little server performance.“.
CPU #
CPU describes the computing power consumed by the processes of your hosting account.
High CPU usage can be caused, for example, by compute-intensive PHP processes, applications, plugins, cron jobs, or a very large number of requests to be processed simultaneously.
A brief spike is not automatically problematic. The situation becomes more interesting when a limit is reached regularly or over a longer period of time while performance issues occur at the same time.
RAM #
The main memory or Memory is required by running processes of your hosting account.
When an application consumes an unusual amount of memory or many processes are active simultaneously, memory usage can increase accordingly.
The CloudLinux RAM of a hosting account should not be confused with the PHP value memory_limit be confused. Both involve memory, but describe different limitations.
Important: A PHP
memory_limitand a CloudLinux memory limit are not the same thing. Increasing a PHP value therefore does not automatically fix a reached hosting resource limit.
I/O #
I/O stands for input/output and refers to the speed of read and write operations on the storage system.
Many or extensive file operations can increase I/O usage. This can occur, for example, during certain backup processes, imports, extensive file operations, or data-intensive applications.
IOPS #
IOPS describes the number of input/output operations executed within a given time period.
I/O and IOPS are related to storage access, but they do not measure the same thing. I/O refers to the transferred data rate, while IOPS looks at the number of operations.
Entry Processes #
Entry Processes – often referred to as EP – describe, in simple terms, the incoming web requests and corresponding processes being simultaneously processed within the CloudLinux environment.
This is not the same as the number of visitors to your website.
A single visitor can generate multiple requests, and a request can take varying lengths of time to process. Long-running processes can therefore also impact concurrent occupancy.
NPROC #
NPROC concerns the number of simultaneously running processes within the hosting account.
This value is also not synonymous with the number of visitors. An account can run various PHP, cron, or other processes without every process corresponding to an individual visitor.
What does reaching a resource limit mean? #
When a resource reaches its intended limit, CloudLinux can restrict further usage of that resource accordingly.
Which impact the user notices depends on which resource is affected and what the website is doing at that moment.
Possible symptoms can include, for example, a slowly responding website, failed processes, or intermittent error messages.
Therefore, the crucial question is not only, Whether "ob" is an abbreviation for something specific or a typo in your source text, it translates to **whether** or **if** in English (from German, for example). If you intended a specific context, please provide the full sentence. a limit has been reached, but which Limit, when and how often.
A detailed explanation of the individual CloudLinux values follows below Understanding CloudLinux Resource Usage in cPanel.
Resource Limit Is Reached #
If a website displays a message like Resource Limit Is Reached indicates that a resource controlled for the hosting account or a corresponding limit plays a role.
The correct reaction is not to indiscriminately disable plugins, delete files, or increase PHP values. First, resource usage should be checked to see which resource was actually affected.
Afterwards, the cause can be investigated specifically.
We will discuss the systematic approach later under Resource Limit Is Reached: Identify and Fix CloudLinux Limits.
Resource consumption and slow website #
A slow website can be related to high resource usage, but it doesn't have to be.
Even slow external services, inefficient database queries, large files, problematic applications, or unfavorable website configurations can affect loading time.
Resource usage is therefore a diagnostic tool and not automatic proof of a specific cause.
Practical Tip: If your website is slow, don't just check the current resource value. Also check the time period when the problem actually occurred. An unremarkable value in the afternoon says little about what happened during an outage in the morning.
Do not confuse visitor numbers and resource consumption #
Many visitors can lead to higher resource consumption. However, there is no simple one-to-one relationship between the two values.
An efficiently operating website can handle many requests with comparatively little effort. A poorly optimized application, on the other hand, can consume significant resources even with just a few visits.
Background processes and cron jobs can also consume resources, even though there are hardly any visitors on the website at that moment.
AWStats and CloudLinux resource usage therefore answer completely different questions.
Which function should you open first in the event of a website error? #
That depends on the visible problem.
If the website shows a specific technical error, Error or the error log is often a good starting point.
If the website responds slowly at times or a resource limit message appears, you should additionally Resource usage check.
If you want to know if and how a specific URL was accessed, you can Visitors or the raw access data to be relevant.
For general visitor statistics, however, tools like AWStats.
Always interpret measured values in context. #
A single value often reveals little about the actual cause of a problem.
A high number of visitors is not automatically problematic. A single error log entry does not necessarily have to be the cause of an outage. A brief CPU spike does not necessarily mean that a website is permanently consuming too many resources.
For a reliable diagnosis, you should compare several pieces of information: the time of the problem, the visible error message, the error log, accesses, and, if applicable, the CloudLinux resource usage.
Important: In the event of a technical malfunction, do not change multiple settings first. First, gather the available information. An error message, a relevant log entry, and the resource history are much more valuable for a targeted diagnosis than speculative changes.
Summary #
The area Measurements Your CURIAWEB cPanel provides you with both statistical information and important data for technical troubleshooting.
Visitors and raw access data show technical web server logs. AWStats and Webalizer process such data statistically. Under bandwidth Do you monitor the transmitted data volumes?.
For technical problems, in particular Error and Resource usage Important. The error log can provide clues regarding specific server or application errors, while the CloudLinux resource usage display shows whether CPU, memory, I/O, or other account resources are playing a role.
The crucial point is not to view the individual measured values in isolation. Only the correlation between the timestamp, error pattern, logs, and resource consumption enables a well-founded diagnosis.
In our advanced guides, we show you step-by-step how to analyze error logs, monitor storage space and bandwidth, and systematically investigate CloudLinux resource issues.
