I think that today no one needs to be convinced of the need for constant monitoring of the network and the devices included in it. Even if, say, the server has been working without failures for a long time, this does not mean that some "well-wishers" will not make a DDoS attack on it. In this case, the only thing that will save you from probable losses is the quick actions taken by the administrator. How do you know when a server has stopped responding? Well, you can periodically go to his web server or connect to FTP. How often will you do this? But won't you forget? And if you went home or are lying in bed with the flu?
Yes, there are more than enough downsides to this approach. But you can somehow automate your work? This is exactly what was developed for this. network visual monitoring program 10-Strike LANState Pro.
Essentially, this program is - sysadmin's eyes and his desktop... While the administrator is busy performing his many duties, LANState Pro will vigilantly monitor the work of the services and network devices entrusted to him. And in a critical situation, he will report the problems to his master. How will he report? Well, it can play the siren, or maybe send an SMS to a given phone number. To do this, you need to either connect your old mobile phone to a computer with LANState Pro, or ask your mobile operator to which address to send an email so that it will be sent as an SMS to your phone. In the second case, the program will need access to the Internet.
In addition, perhaps the most important advantage of LANState Pro is that it can show your network in a graphical form, as you are used to seeing it in project documentation. Each type of device has its own icon, which can be connected by lines of a given style, color and thickness to others. But the most important thing is that the icon can change depending on the state of the physical device assigned to it. The computer turned off - its icon on the network map "went out". Turned on - the icon played with colors again. It is not for nothing that they say that it is better to see once than hear many times. Well, in this case, the admin is likely to hear the yell of a disgruntled user or boss. In order not to take it to such an extreme, it is better to quickly solve the problem. And on the map you can see where everything stopped working.
This is of course all good if the organization is located in the same building and the network is one, you say. But what if there are many branches and they are all in different parts of the city, and in general, in different cities? How, then, can you see a map of their networks and the status of devices? Yes, easily!
As a rule, the connection between the branches is established via VPN or something else. If there is access to the branch office computers from the central office using at least some protocol (let them ping at least), then there are no problems - you create several network maps and the program monitors them simultaneously. You can quickly switch between maps using special link icons.
What if there is no VPN? Problem? No - again, no question, LANState Pro also "shoots" here. The program implements built-in web server with which you can view the network map in a browser window. All that is needed for this is the presence of a physical server in the branches, with access to it via the HTTP protocol over the Internet (or your own channel, again). The monitoring scheme in this case looks like this:
1. Install the LANState Pro program in each branch office on a web server or computer that is accessible from the central office via HTTP. Create a network map, set up monitoring. In the program settings, turn on the web server, set the port, authorization, IP address filter, etc.
2. At the central office, through a browser, connect to the web server of each branch office and see a network map with the status of devices on it. Moreover, by selecting a certain menu item in the icon menu, you can see the response time graph and the detailed state of the test check, with diagnostic messages.
That's it, in two steps you get a network monitoring system for a geographically distributed organization. Something has ceased to work in the branch - you receive a letter by e-mail or SMS. Open a browser - visually assess the situation, plan your further actions. And all this happens quickly. The less equipment downtime, the less likely financial losses. And in some cases, the program may try to fix the problem, even without the participation of the administrator. For example, restart the failed service, restart the computer, execute some special external application or script that will solve the problem on its own in the end. There are a lot of opportunities in the program.
At the same time, the ease of implementation and configuration of the program 10-Strike LANState Pro creates an advantage for it over free, but difficult to configure opensource projects.
Working with a network map in web mode:
View graphs of device response times via the web interface:
Viewing a list of device monitoring checks:
Map context menu:
Download your free 30-day trial now and give it a try!
Programs for monitoring remote computers.
↓ New in the "Monitoring" category:
Free of charge
Alchemy Eye Pro 11.5 / 8.7.4 Rus is an application that will help you conduct network monitoring or constantly monitor the health and status of servers. The Alchemy Eye application will be able to notify the owner or administrator, even if he is not at the computer, by sending an email or SMS.
Free of charge 
NetView 2.94 is an application that can replace the standard Network Neighborhood on your computer. The NetView application will not only replace your standard tools for viewing the network environment, but will also help you keep logs with a list of machines, addresses and descriptions, as well as regularly check the lists for the presence of turned off machines.
Free of charge 
InSSIDer 2.1.1.13 is an application for scanning and viewing information about available Wi-Fi networks. The InSSIDer application allows you to view such parameters of the available network connection points as the signal strength, the channel used, the MAC address of the router and its manufacturer, as well as the SSID and / or public name of the network being viewed.
Free of charge 
Lan Keylogger 1.1.3 is an application that constantly monitors the Internet and local area network. Lan Keylogger application will help to track all the actions of network users and will be most useful when used by administrators with a large number of accountable computers.
Free of charge 
The Dude 3.6 / 4.0 beta 3 is a network scanning application. The Dude application can monitor the operation of devices connected to the network, and also warns the administrator if any problem occurs.
Free of charge 
Essential NetTools 4.3 Build 267 is an application consisting of a set of network utilities that have the ability to diagnose networks and monitor network connections for your computer.
Free of charge 
NetLimiter Pro 3.0.0.11 is an application for monitoring your network traffic. The NetLimiter app will help you monitor every application that uses Internet access or actively manages traffic and controls the speed for the data flow.
Free of charge 
Iris Network Traffic Analyzer 4.0.7 Beta 1 is the coolest traffic sniffer and monitor. The Iris Network Traffic Analyzer application is easy to configure and intercepts all data.
Free of charge 
CommView 6.1 Build 678 is an application for intercepting and analyzing traffic passing through your local network and the Internet. CommView does the job of collecting the data that passes through your modem and then decodes it.
Free of charge 
Network Inventory of Office Equipment 1.0 is a convenient application that relieves IT specialists from the responsibilities of routine inventory of office equipment. The application "Network inventory of office equipment" makes it possible to keep records of the material part, the repairs performed and the installed software. The application is divided into two parts: resident and server.
Free of charge 
Inventory of Computers on the Network 3.95.1755 is a tool for automatic inventory of computer networks. The program "Inventory of Computers on the Web" can display all information about hardware or software in the form of a report, with a choice of any combination of parameters.
Free of charge 
AdmAssistant 1.1 is a free program with the ability to remotely control computers in a local network, as well as having the ability to unconfigure and inventory remote computers. The program also allows you to restart or shut down a remote computer, as well as install the necessary programs on it or remove unnecessary ones.
If you need a tool for complete monitoring and control of your computer via a mobile device, then PC Monitor is what you need. Now I will briefly talk about the principle of operation of this service: on the developer's website, you download a client program for the computer that you want to monitor and which you want to control remotely. After downloading and installing the software, you will be prompted to create your account to use the system. After that, all that remains is to download the application for the operating system of your mobile device and log in to the system.
Now about the supported platforms. You can monitor and manage computers running Windows XP and later, as well as popular Linux distributions. The lack of support for Mac OS is a little disappointing. Below are direct links to download the client for different OS versions:
Among the supported platforms for devices from which the remote computer is monitored and controlled, there are iOS version 4.0 and higher, Android version 2.1 and higher, as well as Windows Phone 7. You can download the mobile client for your device by following these links:
- PC Monitor for Android (version for smartphones and tablets)
- PC Monitor for iOS (iPhone, iPad and iPod Touch version)
Even more pleasing is the ability to control a computer from any other computer through a special admin panel, which can be downloaded (Windows 32 bit) and (Windows 64 bit). Or just log in to the service through any web browser and manage your system.
The free version allows you to work with three computers at the same time. If you need to work with a large number of machines, you will have to buy an additional license. The cost ranges from € 59 per year for 10 computers to € 399 for 100 computers.
And now about what this program can monitor:
- Status and uptime of all your computers
- Current CPU and memory load with the ability to view load statistics
- Your computer's IP address and location as determined by GeoIP
- Ping to your computer with the ability to view statistics
- Status and view of hard drives
- Services and services status
- Status of network interfaces with the ability to view statistics
- Currently running processes
- Log of events in the system
- Scheduled Tasks Status
- List of all users logged into the system (local and remote)
- Information about the state of iron (temperature of the CPU, hard drives, rotational speed of coolers)
- Search and view groups, user accounts and their statuses in Active Directory
- System performance counter
Below are some of the things you can do remotely:
- Starting and stopping any service
- Terminating processes
- Starting and stopping scheduled tasks
- Disconnect any user from the system
- Sending messages to all users authorized in the system
- Using the command line
- Restarting, shutting down and turning on the computer
- Managing user groups, accounts and passwords in Active Directory
- Find and install Windows updates
- Monitoring and managing Exchange
- Hyper-V support
- Manage the list of mobile devices that can send system commands to the computer
The program can send notifications about events taking place on the computer:
- Unplanned service interruption
- Logging different users into the system
- Deviation from normal values of ping rates, CPU and memory load, hard disk fullness, iron readings
- Certain events in the system log
A huge plus is the use of SSL for communication between a computer and a mobile device, which significantly increases the level of security. In general, the service is a full-fledged system for remote monitoring and control of your computers using mobile devices and other computers, which has wide functionality and many useful features. Setting up is easy and very fast. If you have any difficulties, you can always refer to the manual on the developer's website.
Dmitry GanzhaRMON, or Remote MONitoring MIB, was developed by the IETF to support monitoring and analysis of protocols over Ethernet and Token Ring LANs. This standard specification provides much of the same functionality as custom network and protocol analyzers.
Work on the RMON-1 MIB began with the establishment of the RMON working group by the IETF in 1990. A proposal for the standard was published in RFC 1271 in November 1991 and was specific to Ethernet (see Table 1). An additional group for Token Ring was proposed in RFC 1513 in 1993. With the advent of interoperable RMON-1 implementations, the MIB was given draft standard status in RFC 1757 in 1994. In the summer of the same year, the RMON-2 working group began preparing a standard for the extension of RMON-1. Her efforts were subsequently reflected in RFCs 2021 and 2074.
RMON VERSUS SNMP
With all its indisputable advantages, the SNMP infrastructure has a number of significant disadvantages from the point of view of its use in large corporate networks. In accordance with the adopted model, the network management station polls its agents about the values of all counters at regular intervals. The volume of control traffic is such that it itself can cause congestion, especially if it is carried over WAN links. In addition, the entire burden of collecting and processing information is assigned to the control station, and the complexity increases in proportion to the increase in the number of controlled devices. However, the most serious flaw in the original SNMP specification is that the MIB-1 and MIB-2 only provide data for each monitored system individually. So, SNMP managers can provide data on the volume of incoming and outgoing traffic for a specific device, but not a picture of traffic in the entire segment, and even more so in the entire network (in any case, they cannot receive this information directly from their agents).
RMON was created in such a way that data collection and processing are carried out by remote probes. This reduces SNMP traffic on the network and the load on the management station, and information is sent to the station only when needed. RMON applications located in different parts of the network can simultaneously communicate and receive information from the same probe.
McConnel Consulting's research shows that, compared to traditional management tools, using RMON allows the same administrative staff to support two and a half times more users and segments (although this benefit is achieved only in relatively large networks).
ARCHITECTURE RMON
Like SNMP, RMON infrastructure relies on a client / server architecture. In this case, the role of the "client" is the application running on the network management station, and the role of the "server" is the monitoring devices distributed over the network and busy with the collection of information. Monitoring devices are called "probes" and the software they run is called "agents". RMON agents can be located on stand-alone devices or embedded in hubs, switches, routers, and other network devices. The Network Management Station and distributed RMON probes communicate over the network using SNMP.
USE STRATEGY
It can be easier to diagnose a problem after it has occurred than to prevent it, but that means wasting time for users. With RMON, an administrator can proactively manage their network, that is, identify problems before they occur. The key to implementing this strategy is to establish a typical traffic pattern and set thresholds to warn of network traffic deviating from standard patterns.
Table 1. RMON Groups for Ethernet |
|
| Name | Description |
| Statictics | Statistics on octets and packets (including multicast and broadcast), errors, and packet size. |
| History | Distribution of variables of the first group for a certain period at specified intervals. |
| Host | Traffic information for each host in the segment. |
| Host TopN | Sorted data by the specified number of hosts, in descending order. |
| Matrix | Statistics on conversations between pairs of hosts, including the amount of traffic and the number of errors in both directions. |
| Filter | Definitions of templates for collecting packages. |
| Packet Capture | Collect a specified number of packets that match a specified pattern. |
| Alarm | Counter thresholds for signaling changes in network performance. |
| Event | Logging events and determining actions when they occur. |
First of all, the administrator needs to collect data on network performance and utilization over a period of time, which he can rely on as a baseline. Such data can be, for example, information about the number of broadcast, multicast and error packets. The resulting values can then be averaged to find typical deviations from these values. The found deviations can serve as guidelines for setting thresholds.
Setting thresholds is a whole art, and only experience can help the administrator. If the thresholds are set too low, the administrator will receive an unreasonably large number of warnings; if the thresholds are set too high, then he may miss the moment of accumulation of negative trends in the network. In addition, a short-term deviation from the usual traffic pattern often does not affect the overall operation of the network in any way, therefore, the thresholds should be set so that the administrator does not have to be distracted by temporary self-liquidating problems later.
However, no network is static, so the traffic pattern changes over time. Analysis of trends using the History and Statistics groups allows, for example, to identify the moment when the network fails to cope with the proposed load, that is, when its bandwidth needs to be increased.
MONITORING SWITCHED NETWORKS
In shared LANs, each segment must have its own RMON probe if the administrator wants to know about the traffic in it. The same is true for switched LANs, but they have a much larger number of segments. Connecting a separate stand-alone probe to each port on the switch would be a solution, but very expensive. Fortunately, this is far from the only possible approach.
One of the palliative solutions is to connect a hub with its own built-in agent to each switch port instead of a standalone agent, especially since it often does not differ in its functionality. However, such a solution is not always feasible and advisable, in particular, sometimes the switch port is designed to connect only one station or server.
Many manufacturers now build remote monitoring support directly into their switches, but do so in different ways. One solution is to provide a monitoring port on the switch to which all traffic from the specified port is copied. The disadvantage of this approach is obvious - the connected probe can monitor only one switch port at a time and does not see the overall picture of traffic through the switch. Another solution is to implement embedded agents on each port, but vendors tend to limit themselves to just a few RMON groups.
An original approach was proposed by 3Com in its Desktop RMON - software agents are installed directly on a workstation and use its resources to collect statistics (while the network card must work in the mode of receiving all packets). This solution allows you to unload the switch and collect statistics on its operation in full - for this, it is enough to install the software on at least one station in the segment.
RMON-2 VERSUS RMON-1
However, RMON-1 had its limitations. In particular, because it was operating at the MAC layer, the RMON probe could not determine the actual sender of a packet that entered the local segment through the router. Figuratively speaking, the outlook of RMON-1 was limited to one segment at the MAC level. To be able to identify the source (or destination) of traffic on the other side of the router, the probe or agent must be able to identify traffic at the network layer. This would allow him to provide statistics on all hosts who only access the segment, regardless of their location. To this end, the RMON-2 standard defines a specification for monitoring network traffic at and above the network layer.
RMON-2 is not a superset or replacement for RMON-1 - they are logically complementary (see Figure 1). Thus, the most preferable place for RMON-1 probes is the segment, where they will be most useful for detecting physical errors, collecting statistics on stations, etc .; and for RMON-2 probes, the backbone where they are in the best position to collect statistics about the traffic pattern at the network and application layers.
Picture 1. Together, the RMON-1 and RMON-2 MIBs collect traffic statistics across all layers of the OSI model.
RMON-2 has much more powerful filtering capabilities because it has to deal with traffic from many more protocols and at higher layers.
WHAT CAN RMON-2 DO?
The most obvious and attractive feature of RMON-2 is traffic monitoring at the network and application layers. The standard defines nine more groups (see Table 2). Below we will briefly consider why each of them is needed and what information the administrator can extract from the data they contain.
The Protocol Directory group allows the management application to know which protocol (s) a particular agent implements. This information is essential if the application and agent are written by different developers.
Table 2. RMON-2 groups |
|
| Name | Description |
| Protocol Directory | List of protocols the probe can monitor for packets. |
| Protocol distribution | Traffic statistics for each protocol with information on distribution and trends in protocol usage. |
| Address mapping | The correspondence between the addresses of the network and MAC layers. |
| Network-Layer Host | Traffic statistics from and to each detected host. |
| Network-Layer Matrix | Traffic statistics about conversations between host pairs. |
| Application-Layer Host | Traffic statistics from and to each host by protocol. |
| Application-Layer Host | Traffic statistics about conversations between pairs of hosts by protocols. |
| User History Collection | Periodic samples for user-defined variables. |
| Probe Configuration | Remote configuration of probe parameters. |
The Address Translation group establishes a relationship between network and MAC layer addresses. Based on this data, the administrator can, for example, identify which stations have the same IP address.
The Network-Layer Host, Network-Layer Matrix, Application-Layer Host and Application-Layer Matrix groups are designed to collect statistics about the traffic of hosts and host pairs at the network and application levels. Based on these statistics, the administrator can determine which clients are communicating with which servers, so that systems can be redistributed between network segments to optimize traffic flows.
The User History Collection group allows the administrator to configure the collection of statistics for a certain period of time on any of the available counters, for example, for a file server or connection between routers (in RMON-1 this could be done only for predefined counters), and the Probe Configuration group can be configured remotely probe from another developer.
PRACTICAL EXAMPLE
In his research "RMON Methodology. Towards a Successful Distributed Management Implementation" John McConnell, head of McConnel Consulting, provides a number of interesting examples of how RMON is used in practice.
The municipality of one American city was faced with the fact that periodically the server response time increased to unacceptable levels. At first, users reported that they were unable to access UNIX servers over TCP / IP. After an hour or so, similar problems began to arise with other protocols and services. In the end, the administrator was forced to overload the servers. However, after some time, the problem reappeared.
As a result, the administrator decided to install multiple RMON probes on the local network. He immediately discovered that the share of broadcast packets accounted for over 40% of all traffic. Based on this, the administrator configured filters on the probes to collect only broadcast packets. This allowed us to establish that multiple servers were sending ARP requests unnecessarily frequently. By configuring filters to collect packets during dialogs between specific pairs of servers and clients, he established that for each client request, the server sends not a response, but an ARP request.
After analyzing the information received, the administrator realized that the server loses information about the client's address as soon as it receives it (in other words, that the ARP cache was continuously updated). After checking the configuration of one of the servers, he discovered that the ARP cache timeout was incorrectly set in milliseconds. Changing the timeout value resolved the problem.
INSTEAD OF CONCLUSION
The benefits of RMON are clear. Without leaving his workplace, the administrator can see all traffic in the local segment regardless of its actual physical location - in the same room or on the other side of the world. Knowing the traffic picture, the administrator can identify trends, bottlenecks and problem situations. If a problem arises, the administrator does not need to rush to the call and install the protocol analyzer, since he already has a powerful distributed diagnostic tool at his disposal - the probe is ready to transfer the traffic data accumulated during its operation to the console on demand.
Dmitry Ganzha is the executive editor of LAN. You can contact him at:
In the previous article, I compiled a list of 80 tools for monitoring a Linux system. It also made sense to make a selection of tools for the Windows system. Below is a list that serves only as a starting point, there is no rating here.
1. Task Manager
The well-known Windows Task Manager is a utility for displaying a list of running processes and the resources they consume. But do you know how to use its full potential? As a rule, it is used to monitor the state of the processor and memory, but you can go much further. This application is pre-installed on all Microsoft operating systems.
2. Resource Monitor
A great tool to estimate CPU, RAM, network and disk usage in Windows. It allows you to quickly get all the information you need about the health of critical servers.
3. Performance Monitor
The main tool for managing Windows performance counters. Performance Monitor, in earlier versions of Windows, is known to us as Performance Monitor. The utility has several display modes, displays performance counters in real time, saves data to log files for later study.
4.Reliability Monitor
Reliability Monitor - System stability monitor, allows you to track any changes in computer performance, you can find the stability monitor in Windows 7, in Windows 8: Control Panel> System and Security> Action Center. With the help of Reliability Monitor, you can keep a record of changes and failures on the computer, the data will be displayed in a convenient graphical form, which will allow you to track which application and when caused an error or freeze, track the appearance of the Windows blue screen of death, the reason for its appearance (another Windows update or program installation).
5. Microsoft SysInternals
SysInternals is a complete suite of programs for administering and monitoring Windows computers. You can download them yourself for free on the Microsoft website. Sysinternals tools help you manage, troubleshoot, and diagnose Windows applications and operating systems.
6. SCOM (part of Microsoft System Center)
System Center is a complete set of tools for IT infrastructure management, with which you can manage, deploy, monitor, configure Microsoft software (Windows, IIS, SQLServer, Exchange, and so on). Alas, MSC is not free. SCOM is used for proactive monitoring of key IT infrastructure assets.
Monitoring Windows Servers with the Nagios Family
7. Nagios
Nagios has been the most popular infrastructure monitoring tool for several years (for Linux and Windows). If you are considering Nagios for Windows, then install and configure the agent on the Windows server. NSClient ++ monitors the system in real time and provides outputs from a remote monitoring server and more.
8. Cacti
Usually used in conjunction with Nagios, it provides the user with a convenient web interface to the RRDTool utility designed to work with Round Robin Databases, which are used to store information about changes in one or more values over a certain period of time. Statistics in network devices is presented in the form of a tree, the structure of which is set by the user himself, you can build a graph of channel use, use of HDD partitions, display resource latency, etc.
9. Shinken
Flexible, scalable open source monitoring system based on the Nagios core written in Python. It is 5 times faster than Nagios. Shinken is compatible with Nagios, it is possible to use its plugins and configurations without making adjustments or additional configuration.
10. Icinga
Another popular open monitoring system that checks hosts and services and reports their status to the administrator. As a fork of Nagios, Icinga is compatible with it and they have a lot in common.
11. OpsView
OpsView was originally free. Now, alas, users of this monitoring system have to fork out.
Op5 is another open source monitoring system. Graphing, storing and collecting data.
Nagios alternatives
13. ZabbixOpen source software for monitoring and tracking the statuses of various services of a computer network, servers and network equipment, is used to obtain data on processor load, network utilization, disk space, and the like.
14. Munin
Not a bad monitoring system that collects data from several servers at the same time and displays everything in the form of graphs, with which you can track all past events on the server.
15. Zenoss
Written in Python using Zope Application Server, data is stored in MySQL. With Zenoss you can
monitor network services, system resources, device performance, the Zenoss core analyzes the environment. This makes it possible to quickly deal with a large number of specific devices.
16. Observium
A system for monitoring and monitoring network devices and servers, although the list of supported devices is huge and is not limited only to network devices, the device must support SNMP.
17. Centreon
An integrated monitoring system, allows you to control the entire infrastructure and applications containing system information. Free alternative to Nagios.
18. Ganglia
Ganglia is a scalable distributed monitoring system used in high performance computing systems such as clusters and grids. Tracks statistics and computation history in real time for each of the monitored nodes.
19. Pandora FMS
Monitoring system, good productivity and scalability, one monitoring server can control the work of several thousand hosts.
20. NetXMS
Open source software for monitoring computer systems and networks.
21. OpenNMS
OpenNMS monitoring platform. Unlike Nagios, it supports SNMP, WMI and JMX.
22. HypericHQ
A component of the VMware vRealize Operations suite, it is used to monitor OS, middleware and applications in physical, virtual and cloud environments. Displays availability, performance, usage, events, logs, and changes at each level of the virtualization stack (from the vSphere hypervisor to the guest OS).
23. Bosun
An open source alert system from StackExchange. Bosun has a well-thought-out data schema as well as a powerful processing language.
24. Sensu
Sensu is an open source paging system similar to Nagios. There is a simple dashboard, you can see a list of clients, checks and triggered alerts. The framework provides the mechanisms that are needed to collect and accumulate server statistics. Each server runs the Sensu agent (client), which uses a set of scripts to check the health of services, their state and collect any other information.
25. CollectM
CollectM collects statistics on system resource usage every 10 seconds. It can collect statistics for several hosts and send it to the server, the information is displayed using graphs.
28. Performance Analysis of Logs (PAL) Tool
34. Total Network Monitor
This is a program for constant monitoring of the work of the local network of individual computers, network and system services. Total Network Monitor generates a report and notifies you about the errors that have occurred. You can check any aspect of a service, server or file system: FTP, POP / SMTP, HTTP, IMAP, Registry, Event Log, Service State and others.
35. PRTG
38. Idera
Supports multiple operating systems and virtualization technologies. There are many free tools that you can use to monitor the system.
39. PowerAdmin
PowerAdmin is a commercial monitoring solution.
40. ELM Enterprise Manager
ELM Enterprise Manager - full monitoring from "what happened" to "what is happening" in real time. Monitoring tools in ELM include - Event Collector, Performance Monitor, Service Monitor, Process Monitor, File Monitor, PING Monitor.
41. EventsEntry
42. Veeam ONE
An efficient solution for monitoring, reporting and scheduling resources in the environment of VMware, Hyper-V and Veeam Backup & Replication infrastructure, monitors the state of the IT infrastructure and diagnoses problems before they interfere with the user experience.
43. CA Unified Infrastructure Management (formerly CA Nimsoft Monitor, Unicenter)
Monitors the performance and availability of Windows server resources.
44. HP Operations Manager
This infrastructure monitoring software performs proactive root cause analysis to reduce recovery time and operational management costs. The solution is ideal for automated monitoring.
45. Dell OpenManage
OpenManage (now Dell Enterprise Systems Management) is an all-in-one monitoring product.
46. Halcyon Windows Server Manager
Management and monitoring of networks, applications and infrastructure.
Below is a list of the (most popular) network monitoring tools
54. Ntop
55. NeDi
Nedi is an open source network monitoring tool.
54. The Dude
The monitoring system Dude, although free, but according to experts, is in no way inferior to commercial products, monitors individual servers, networks and network services.
55. BandwidthD
Open source software.
56. NagVis
Extension for Nagios, allows you to create infrastructure maps and display their status. NagVis supports a wide variety of widgets, icon sets.
57. Proc Net Monitor
A free monitoring application that allows you to track all active processes and, if necessary, quickly stop them in order to reduce the load on the processor.
58. PingPlotter
Used to diagnose IP networks, to determine where network packet loss and delays are occurring.
Small but useful tools
The list would not be complete without mentioning several hardware monitoring options.60. Glint Computer Activity Monitor
61. RealTemp
A utility for monitoring temperatures of Intel processors, it does not require installation, monitors the current, minimum and maximum temperatures for each core and the start of throttling.
62. SpeedFan
A utility that allows you to control the temperature and rotational speed of the fans in the system, monitors the indicators of the sensors of the motherboard, video card and hard drives.
63. OpenHardwareMonitor
