...
Monitoring can be performed manually by using Task Manager. Task Manager provides information about applications currently running on your system, the processes and memory usage or other data about those processes, and statistics about memory and processor performance. Although useful as a quick reference to system operation and performance, Task Manager lacks the logging and alert capabilities so it should be used as a current real time reference of how the server is operating "now".
The first time you open task manager on Windows Server, you will be presented with a minimal display.
...
By clicking "More Details" it reveals more details.
...
Using the more details view, we can see how any process is doing (CPU, Memory, Disk and Network) and what load it is adding to the server. This will be helpful for troubleshooting slow response issues just by looking at it and quickly know who's using the most of the disk, memory or network bandwidth.
...
If you expand a process, you will see more detail such as CPU, memory disk and network used by the process. For example, expanding the "Service Host : Network Service" you will be able to see the services that are running inside it.
...
If you want to stop a service, you can do it by right-clicking on it.
...
The "Performance" tab make it easy to get all the required information about the server performance in one place.
CPU Usage : Shows all the information you need to know about your CPU, Type of CPU, Clock speed, Total sockets, the number of cores, number of the logical processors being exposed to the OS and also if the CPU supports virtualization or not.
This tab also shows the CPU usage since the Task Manager was opened.
Memory: This tab displays information about:
...
| Anchor | ||||
|---|---|---|---|---|
|
...
Event Viewer provides historical information that can help troubleshooting, track down system and security issues. The Window Logs category that are available:
Application, Security,
Setup, System,
Forwarded Events, and
Applications and Services
...
Application Log: Records events logged by applications. For example, a SQL Database might record a database connection error.
Security Log: Records Re
...
cords events such as valid and invalid logon attempts, creating\deleting files or other objects. Records events that you have set for auditing with local or global group policies (GPOs).
...
Setup Log: Records events related to application setup.
...
System Log: Records events logged and predetermined by Windows system components. For example, failure of a driver, failure of system component to load at startup.
...
Forwarded Events Log: It is used to store events collected from remote computers. To collect events from remote computers, you must create an event subscription. To learn about it, see Event Subsciption on Microsoft Technet site.
...
Application And Service Logs: Records events from a single application or component instead that event that might have system wide impact.
...
The following table lists the common event properties:
...
Proporty Name | Description |
Source | |
Event ID | |
Level | |
User | |
Option code | |
Log | |
Task Category | |
Keyword | |
Computer | |
Date and time |
...
Go to "Start" -> "Run".
Write "CMD" and press on "Enter" key.
Write the command "net statistics server" and press on "Enter" key.
The line that start with "Statistics since …" provides the time that the server was up from.
...
System Statistics Section:
NOTE: The statistics displayed on this screen are computed independently on various time scales and
schedules. As a result, they may update at different times.
...
The Field | Display |
Receive Rate (a time-based chart in events/minute) | How busy the server is at a given instant – the rate at which the server is receiving data from all collectors. |
Archive Compression (% compression) | The current effect of archive data compression. If the value is zero, it indicates that archive compression is either ineffective or turned off. To increase the effect of data compression, increase the value of archive compression deadbands on individual tags in the Tag Maintenance screen to activate compression. In computing the effect of archive compression, Historian counts internal system tags as well as data source tags. Therefore, when working with a very small number of tags and with compression disabled on data source tags, this field may indicate a value other than zero. If you use a realistic number of tags, however, system tags will constitute a very small percentage of total tags and will therefore not cause a significant error in computing the effect of archive compression on the total system. |
Write Cache Hit | The hit ratio of the write cache in percent of total writes. It is a measure of how efficiently the system is collecting data and should typically range from 95 to 99.99%. If the data is changing rapidly over a wide range, however, the hit percentage drops significantly because current values differ from recently cached values. More regular sampling may increase the hit percentage. Out of order data also reduces the hit ratio. |
Failed Writes | The number of samples that failed to be written. Since failed writes are a measure of system malfunctions or an indication of offline archive problems, the value shown in the display should be zero. If you observe a non-zero value, investigate the cause of the problem and take corrective action. The Historian also generates a message if a write fails. Note that the message only appears once per tag, for a succession of failed writes associated with that tag. For example, if the number displayed in this field is 20, but they all pertain to one Historian tag, you will only receive one message until the Historian tag is healthy again. |
Messages Since Startup | A count of system messages generated since the last startup. The system resets the value to zero on restart. The message database, however, may contain more messages than this number indicates. |
...
The Message Search screen, shown in the following figure, lets you enter search parameters, such as start and end times, and to limit the search to alerts only or messages only. It further refines the search by topic and a text mask.
...
Enter a start time and end time (required). If your start date and end date are identical, you must enter a timestamp with the date.
Select All, Alerts, or Messages.
Select a Topic (optional).
Enter a text mask (optional). If you do not specify a text mask, all items for the associated alert or message will be returned. Use a text substring for a mask. The Message contains field does not accept wildcards.
...