Good network monitoring and management programs help the administrator:

identify conditions that lead to problems;

decide network problems;

prevent network failures.

Since this approach saves time and money, saves equipment, data and user nerves, in the long run it will be preferred over finding out the causes of the failure after it has occurred.

If network management is done correctly, it can also be seen as a proactive solution to problems. ISO has identified five categories of network management that are directly related to proactive problem solving.

1.Manage accounts for registering and issuing reports on the operation of network resources.

2.Configuration management to control network components and their parameters.

3. Failure prevention to find and isolate network problems.

4.Performance management to monitor, analyze and control data flows in the network.

5.Security management to track and control access to network resources.

Controls are means of solving problems. At first, it will take you some time to understand what statistical information you should receive on a regular basis. You will have to collect data in order to then draw conclusions about the characteristics of normal network operation. By knowing how the network should operate normally, you can monitor changes in this data (they often indicate potential problems in the network).

Modern network operating systems have built-in network monitoring utilities. They will help you monitor the operation of the network, build a reference graph of its behavior (as part of a program for early troubleshooting). These tools use three types of information:

event logs, which record errors, actions and situations affecting

security system, or other facts important for diagnosing problems;

resource access statistics, which stores information about who uses network resources and how;

performance statistics that reflect CPU load, server throughput and memory usage.

MicrosoftWindowsNTServer, for example, has a PerformanceMonitor utility that provides an overall picture of the state and activity of the system.

A network administrator can use PerformanceMonitor:

to analyze network operation both in real time and in recording;

identifying trends in its work;

identifying bottlenecks;

recording the effects of changes in the system and configuration;

definitions bandwidth systems;

monitoring local or remote computers;

notifications to administrators about critical events;

CPU performance tracking, hard drives, memory and processes;

viewing key parameters systems as a whole.

Reference chart

Knowing how the network behaves during normal operating conditions is just as important as knowing how to troubleshoot the problems that caused the network to fail. Monitoring and documenting in detail the normal operation of your network will give you information from which you can create a reference graph of its behavior. And in case of any problems, you will compare the current behavior of the network with the reference one.

The reference schedule is created in advance when the network is functioning normally. It will help you determine:

general picture of network congestion during the day;

narrow places;

an overall picture of network usage by individual computers;

an overall picture of the schedule of various protocols.

The PerformanceMonitor utility is designed to monitor computer performance in real time, which allows you to find almost all bottlenecks. Figure 8.4 shows the %ProcessorTime curve, which reaches 100 percent. If this happens frequently (over a long period this figure is close to 100 percent), the bottleneck is the processor.

By analyzing the system behavior graph, you can prevent problems from arising, since it will tell you:

the network must be divided into several segments;

the number of file servers should be increased;

it is necessary to replace network adapters with more efficient ones.

Network management programs and proactive troubleshooting

Modern network management software offers a number of measures that will lead to proactive resolution of network problems.

Cross control and constant monitoring interacting network components (to ensure that a failure in one component does not look like a failure in another, healthy one).

Identifying invalid or erroneous packets.

Periodic inspection of network components, testing of interfaces and monitoring of network activities.

Notification of the need to expand the network with new computers (or other components) and technologies.

Maintain a log (file) of errors (in adapters, cables and other components) and notify the administrator about them. Advanced management programs may even offer you one of the solutions to the problem.

Monitoring the operation of servers (including print servers and gateways), recording the results and notifying the administrator in case of network problems.

Maintaining network traffic history and error statistics. This includes information about the status of routes between computers and between LANs.

The management program can save all the interesting information in its log and import it into other files or databases. To present this information in a different form, the administrator must use other application programs.

IN large network good programs management transmits this information to a central computer, where the administrator typically stores a detailed history of the remote LAN.

Summary

Network management is a multifaceted process. It also includes monitoring network behavior, which can be seen as a way to proactively troubleshoot problems. If planning, monitoring and management are carried out correctly, then problems will arise much less frequently. When planning a network, an administrator must implement concepts and procedures designed with one goal in mind: preventing a problem before it occurs. These plans include backup, unification, continuous improvement and documentation.

The network administrator is helped to solve these problems special utilities. WindowsNT has built-in network monitoring and management programs that keep statistics on performance and resource access, as well as event logs.

An important part of network management is a reference graph of its behavior. It is created gradually, and very carefully and in detail. If the network begins to fail, the administrator should first refer to this graph. It compares current workload graphs with it, looks for potential bottlenecks, analyzes the number of errors and general statistics productivity.

Solving network problems

Methodology

Despite the most sophisticated plans, monitoring and support, network problems will still arise. A network administrator or support engineer will be able to identify and resolve them more quickly if they take a structured approach rather than trying to apply all possible solutions one at a time.

Structural approach

The structured approach consists of five steps.

1. Determining the priority of the problem.

2.Collect information to identify symptoms.

3. List development possible reasons.

4. Isolation of the problem.

5.Analysis of inspection results to develop a solution.

Determining Priority

The first step in a structured approach is to categorize problems according to their importance. Every user naturally wants his computer to be “fixed” before others. Therefore, first, the administrator or support engineer, having received a signal about a problem, must set its priority.

Setting priorities for solving network problems means determining the degree of impact each problem will have on the network. For example, the board in the monitor burned out and it stopped working. The board simply needs to be replaced, which is much less interesting for the administrator than dealing with someone's CD-ROM drive or sound system. But it's probably more important to fix the user's monitor than the gamer's CD-ROM.

You cannot solve all problems at once. And do they all require an immediate solution? What problems need to be solved first?

Collection of information

Collecting information is the foundation for error-free problem isolation. The administrator must have a reference graph of network behavior to compare its current behavior with. In addition, while gathering information, you need to inspect the network and identify obvious causes of the problem. Quick review must include verification! network documentation to find out if this problem has occurred before and what solution was adopted.

User survey

If you ask users the right questions, their answers will help clarify the situation. The engineer should ask, “Why do you think the network is not OK?” The following user observations may tell you the symptoms of the problem.

"The network is slow."

"I can't contact the server."

"I was connected to the server, but the connection was lost."

"One of my apps isn't working."

"I can't print on the printer."

An experienced administrator or support engineer, taking into account the user's observations, asks him a series of questions like or or And Not really, to narrow down the possible causes. For example:

Who was affected by the failure: everyone, someone in particular, or randomly one or another user?

Is the entire network down or just one computer?

Did this problem occur before the upgrade?

Does this problem happen all the time or does it happen from time to time?

Does this problem occur with all applications or with just one?

Has there been anything similar before?

Have new users appeared on the network? Has new equipment appeared on the network?

Was there any application installed before the problem occurred? Were they moved to Lately any equipment?

Which suppliers' products are involved?

Is there any pattern of problems associated with a specific vendor or specific components (cards, hubs, disk drives, application programs or network software)?

Has anyone tried to solve this problem?

In addition, the network administrator or support engineer should consider the following factors:

application versions, operating systems and other software;

changing the configuration of network components or the network operating system.

When you become a network administrator or support engineer, you will become more familiar with the components and application programs your network and you will guess where to look first for possible causes of problems.

Dividing the network into segments

If a preliminary inspection of the network does not reveal the cause of the problem, the administrator or support engineer should mentally break the network into as many segments as possible so that they are dealing with a small portion of the network rather than the entire network.

Having identified the segment in which the problem is supposedly hidden, the administrator or support engineer should check all the components of this segment in turn:

adapters;

concentrators;

cables and connectors;

connecting components (repeaters, bridges, routers and gateways);

protocols.

Particular attention should be paid network protocols: They are designed specifically to try to overcome any network errors.

Most protocols have a built-in mechanism for retrying failed operations, which tries to automatically restore the network's functionality. The launch of this mechanism is immediately noticeable as the network slows down due to a large number of retries.

This mechanism increases network reliability, but at the same time makes it difficult to identify the causes of some network problems, since the same symptom sometimes indicates several problems.

Here again, a list of questions aimed at narrowing down the range of possible causes will come in handy. At this stage, it is important to understand how each component is supposed to work and what the consequences of its failure may be. A reference graph of network behavior will also be useful.

Questions could be:

What computers can operate on the network?

Can a computer that is not connected to a network work autonomously?

Does the network adapter work on a computer that is not on the network?

Is there normal traffic on the network?

Possible reasons

After summing up all the information you have collected, develop a list of possible causes of the problem. Try to rank them in descending order of likelihood.

Isolating the problem

Choosing the most probable cause, test the “suspected” component and find out whether your guesses are correct. For example, if you suspect that one of the computers has a faulty board network adapter, try replacing it with another one that is known to work.

Analysis of results

If the test confirms your assumption, then the reason (or one of the reasons) has been found. If testing does not produce results. You should do it all over again. And if the list of possible reasons has dried up without revealing the problem. You will either have to return to the information gathering stage or ask for help.

Outside help

Most network administrators and support engineers pride themselves on being able to identify and resolve network problems without outside help. They strive to gain respect and authority as excellent specialists. However, there are situations when it is impossible to do without someone else's intervention.

Firstly, there are other specialists in your company who will certainly help you. Secondly, you can contact technical support hardware or software manufacturer. It would be a good idea to contact the supplier who sold you the network components for information.

The best administrators and support engineers are the ones who know when and where to ask for help (these are the ones that users respect the most).

The previous article compiled a list of 80 monitoring tools Linux systems. It also made sense to make a selection of tools for the Windows system. The following is a list that serves as a starting point only, there is no ranking.

1.Task Manager

Well-known dispatcher Windows tasks- utility for displaying a list 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 operating systems Microsoft.

2. Resource Monitor

A great tool to estimate CPU usage, random access memory, network and disks in Windows. It allows you to quickly get everything necessary information about the status of critical servers.

3.Performance Monitor

The main tool for managing performance counters in Windows. Performance Monitor, in earlier Windows versions known to us as System Monitor. The utility has several display modes, displays performance counters in real time, and saves data to log files for later study.

4.Reliability Monitor

Reliability Monitor - System stability monitor, allows you to monitor any changes in computer performance, you can find the stability monitor in Windows 7, in Windows 8: Control Panel > System and Security > Action Center. Using Reliability Monitor, you can keep track of changes and failures on your 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 froze, track the occurrence of blue screen death of Windows, the reason for its appearance (another Windows update or installing a program).

5.Microsoft SysInternals

SysInternals is full set programs for administering and monitoring computers running Windows OS. You can download them for yourself for free on the Microsoft website. Sysinternals utility programs help manage, troubleshoot, and diagnose applications and operating systems. Windows systems.

6. SCOM (part of Microsoft System Center)

System Center is a complete set of tools for managing IT infrastructure, with which you can manage, deploy, monitor, configure software Microsoft software(Windows, IIS, SQLServer, Exchange, and so on). Unfortunately, MSC is not free. SCOM is used for proactive monitoring of key IT infrastructure objects.

Monitoring Windows servers using 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 Windows server. NSClient++ monitors the system in real time and provides outputs with remote server monitoring and more.

8. Cacti

Typically 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 quantities over a certain period of time. Statistics in network devices are presented in the form of a tree, the structure of which is specified by the user himself; you can build a graph of channel usage, usage HDD partitions, display resource latency, etc.

9. Shinken

Flexible, scalable monitoring system with open source code, based on the Nagios core written in Python. It is 5 times faster than Nagios. Shinken is compatible with Nagios, you can use its plugins and configurations without making adjustments or additional configuration.

10. Icinga

Another popular one open system monitoring, which 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, unfortunately, users of this monitoring system have to shell out money.

Op5 is another open source monitoring system. Plotting, storing and collecting data.

Alternatives to Nagios

13. Zabbix

Open software for monitoring and tracking the status of various computer network services, servers and network equipment, used to obtain data about CPU load, network usage, disk space and the like.

14. Munin

A good monitoring system that collects data from several servers simultaneously and displays everything in the form of graphs, with which you can track all past events on the server.

15.Zenoss

Written on Python language using Zope application server, data is stored in MySQL. With Zenoss you can
monitor network services, system resources,device performance,Zenoss core analyzes the environment. This makes it possible to quickly understand a large number of specific devices.

16. Observium

Monitoring and surveillance system 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

A comprehensive monitoring system allows you to control the entire infrastructure and applications containing system information. Free alternative Nagios.

18. Ganglia

Ganglia - scalable distributed system monitoring, used in high-performance computing systems, such as clusters and grids. Monitors 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 monitor the work of several thousand hosts.

20. NetXMS

Software with open source 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 every level of the virtualization stack (from the vSphere hypervisor to guest OSes).

23. Bosun

Open source monitoring and alert system from StackExchange. Bosun has a well-thought-out data design, as well as a powerful language for processing it.

24. Sensu

Sensu is an open source alert 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 needed to collect and accumulate server operation statistics. Each server runs a Sensu agent (client), which uses a set of scripts to check the functionality of services, their status and collect any other information.

25. CollectM

CollectM collects statistics about 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 constantly monitoring the operation of a local network of individual computers, network and system services. Total Network Monitor generates a report and notifies you about errors that have occurred. You can check any aspect of the 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 your system.

39. PowerAdmin

PowerAdmin is a commercial monitoring solution.

40. ELM Enterprise Manager

ELM Enterprise Manager - complete 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 effective solution for monitoring, reporting and scheduling resources in VMware, Hyper-V and Veeam Backup & Replication infrastructure, monitors the health of your IT infrastructure and diagnoses problems before they interfere with user experience.

43. CA Unified Infrastructure Management (formerly CA Nimsoft Monitor, Unicenter)

Monitors performance and availability Windows resources server.

44. HP Operations Manager

This infrastructure monitoring software performs proactive root cause analysis, reducing recovery time and reducing operations 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 (most popular) network monitoring tools

54.Ntop

55.NeDi

Nedi is an open source network monitoring tool.

54. The Dude

The Dude monitoring system, although free, is in no way inferior, according to experts commercial products, monitors individual servers, networks and network services.

55.BandwidthD

Open source program.

56. NagVis

An extension for Nagios that allows you to create infrastructure maps and display their status. NagVis supports a large number of various 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 to reduce the load on the processor.

58. PingPlotter

Used to diagnose IP networks, allowing you to determine where losses and delays occur network packets.

Small but useful tools

The list wouldn't be complete without mentioning a few hardware monitoring options.

60. Glint Computer Activity Monitor

61.RealTemp

Temperature monitoring utility Intel processors, it does not require installation, monitors current, minimum and maximum values temperatures for each core and start of throttling.

62. SpeedFan

A utility that allows you to control the temperature and fan speeds in the system, monitors sensor readings motherboard, video cards and hard drives.

63.OpenHardwareMonitor

You most likely know that it has a built-in firewall. Perhaps you also know how to allow and block access of individual programs to the network in order to control incoming and outgoing traffic. But did you know that Windows firewall can be used to log all connections passing through it?

Windows Firewall logs can be useful in solving specific problems:

• The program you are using cannot connect to the Internet, although other applications do not experience this problem. In this case, to troubleshoot the problem, you should check whether the system firewall is blocking the connection requests of this program.
• You suspect that the computer is being used to transfer data malware and want to monitor outgoing traffic for suspicious connection requests.
• You have created new rules for allowing and blocking access and want to ensure that the firewall correctly processes the given instructions.

Regardless of the reason for use, enabling event logging can be challenging as it requires a lot of fiddling with the settings. We will give a clear algorithm of actions on how to activate the registration of network activity in the Windows firewall.

Access to firewall settings

First, you need to go to advanced settings Windows Firewall. Open the control panel (click right click mouse on the Start menu, “Control Panel” option), then click the “Windows Firewall” link if the view mode is small/large icons, or select the “System and Security” section, and then “Windows Firewall” if the view mode is category .

In the firewall window, select the option on the left navigation menu “Extra options”.

You will see the following settings screen:

It's internal technical side Windows Firewall. This interface allows you to allow or block access of programs to the Internet, configure incoming and outgoing traffic. In addition, this is where you can activate the event logging feature - although it is not immediately clear where this can be done.

Accessing log settings

First, select the option “Windows Firewall in increased security(Local computer)".

Right-click on it and select the “Properties” option.

A window will open that may confuse the user. When you select three tabs (Domain Profile, Private Profile, Public Profile), you will notice that their content is identical, but relates to three different profiles, the name of which is indicated in the tab title. Each profile tab contains a button to configure logging. Each log will correspond to a different profile, but which profile are you using?

Let's look at what each profile means:

• A domain profile is used to connect to wireless network Wi-Fi when the domain is set by a domain controller. If you're not sure what this means, don't use it. this profile.
• The private profile is used to connect to private networks, including home or personal networks - this is the profile you are most likely to use.
• The general profile is used to connect to public networks, including chains of restaurants, airports, libraries and other institutions.

If you are using a computer in home network, go to the “Private Profile” tab. If you are using a public network, go to the “Public Profile” tab. Click the “Configure” button in the “Logging” section on the correct tab.

Activating the event log

In the window that opens, you can configure the location and maximum size magazine. You can set an easy-to-remember location for the log, but the actual location of the log file doesn't really matter. If you want to start event logging, set both the “Log missed packets” and “Log successful connections” drop-down menus to “Yes” and click the “OK” button. Running this feature all the time can cause performance issues, so only enable it when you really need to monitor connections. To disable the logging feature, set the value to “No (default)” in both drop-down menus.

Studying logs

Now the computer will record network activity controlled by the firewall. To view the logs, go to the “Advanced Settings” window, select the “Monitoring” option in the left list, and then in the “Logging Options” section click the “File Name” link.

The network activity log will then open. The contents of the log may be confusing to an inexperienced user. Let's look at the main contents of the log entries:

1. Date and time of connection.
2. What happened to the connection? The status “ALLOW” means that the firewall allowed the connection, and the status “DROP” indicates that the connection was blocked by the firewall. If you encounter network connection problems separate program, you can determine for sure that the cause of the problem is related to the firewall policy.
3. Connection type - TCP or UDP.
4. In order: IP address of the connection source (computer), destination IP address (for example, a web page) and used on the computer network port. This entry allows you to identify ports that require opening for the software to work. Also watch out for suspicious connections - they could be made by malware.
5. Whether the data packet was successfully sent or received.

The information in the log will help determine the cause of connection problems. The logs can record other activity, such as the target port or TCP acknowledgment number. If you need more details, check out the “#Fields” line at the top of the log to identify the meaning of each metric.

Don't forget to turn off the logging feature when you're done.

Advanced network diagnostics

By using Windows Firewall logging, you can analyze the types of data being processed on your computer. In addition, you can determine the causes of network problems related to the firewall or other objects disrupting connections. The activity log allows you to familiarize yourself with the work of the firewall and get a clear picture of what is happening on the network.

Found a typo? Press Ctrl + Enter

Programs for monitoring remote computers.

↓ New in the "Monitoring" category:

Free
Alchemy Eye Pro 11.5 / 8.7.4 Rus is an application that will help you network monitoring or constantly monitor the performance 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
NetView 2.94 is an application that can replace the standard Network Neighborhood on your computer. NetView will not only replace your standard means to view network environment, but will also help you maintain logs with a list of machines, addresses and descriptions, as well as regularly check lists for the presence of switched off machines.

Free
InSSIDer 2.1.1.13 is an application for scanning and viewing information about available networks Wi-Fi protocol. The InSSIDer application allows you to view parameters of available network connection points, such as signal strength, channel used, MAC address of the router and its manufacturer, as well as the SSID and/or public name of the network being viewed.

Free
Lan Keylogger 1.1.3 is an application that constantly monitors the Internet and local network. The Lan Keylogger application will help track all the actions of network users and will be most useful when used by administrators with a large number of accountable computers.

Free
The Dude 3.6/4.0 beta 3 is a network scanning application. The Dude app can monitor the performance of devices connected to the network and also alert the administrator if any problem occurs.

Free
Essential NetTools 4.3 Build 267 is an application consisting of a set network utilities, which have the ability to conduct network diagnostics and monitoring network connections for your computer.

Free
NetLimiter Pro 3.0.0.11 is an application for monitoring your network traffic. The NetLimiter application will help you monitor every application that uses Internet access or actively manages traffic and control the speed for the data flow.

Free
Iris Network Traffic Analyzer 4.0.7 Beta 1 is the coolest sniffer and traffic monitoring tool. The Iris Network Traffic Analyzer application is easy to configure and intercepts all data.

Free
CommView 6.1 Build 678 is an application for intercepting and analyzing traffic passing through your local network and the Internet. The CommView app does the work of collecting the data that passes through your modem and then decoding it.

Free
Network inventory of office equipment 1.0 is convenient application, freeing IT specialists from the duties of routine inventory of office equipment. The “Network Inventory of Office Equipment” application makes it possible to keep records of material parts, repairs made and installed software. The application is divided into two parts: resident and server.

Free
Inventory of Computers on the Network 3.95.1755 is a tool for automatically conducting inventory computer networks. The program "Inventory of Computers on the Network" can display all information about the hardware or software in the form of a report, with the choice of any combination of parameters.

Free
AdmAssistant 1.1 is free program with an opportunity remote control computers on a local network, as well as having the ability to remove configurations from remote computers and conduct their inventory. The program also allows you to reboot or shut down a remote computer, as well as install on it necessary programs or delete unnecessary ones.

Total Network Monitor 2 is a program for constant monitoring and administration of a local network, individual computers, Internet resources, network and system services. TNM will notify you in advance of problems using a variety of means and generate a detailed report of what happened and when.

Network monitoring

you create monitors- objects that periodically check one or another aspect of the operation of a service, server or file system. The monitors are flexibly configured and display the network status in real time.

If any indicators deviate from the norm, the monitor executes the script described in advance actions: for example, a sound signal, notification by e-mail or IM with a detailed description of the incident, rebooting the remote computer, launching an application, etc.

Turning to network monitoring log, you can always see the history of readings from all monitors and a list of completed actions.

Download for free and start using right now without any functionality limitations!

Health and problem checks

Checks- Total Network Monitor 2 connection with outside world. They provide monitors with data for analysis. In our network monitoring utility you will find many checks for all occasions. Queries via network protocols to monitor servers, check services, event logs and keys Windows registry, searching for a string in a file on a remote computer and much more - TNM does all this with ease.

Checklist

Internet: ICMP TCP HTTP FTP SMTP POP3 IMAP Telnet

Windows: Event Log Service Status Registry Status System Performance

File: File existence File size File comparison Number of files CRC32 file File content Disk space

Alerts and event history

Actions are triggered as soon as something goes wrong. They notify you so that you can fix everything in time. They can provide first aid in administering the local network: restart the service or remote computer, launch the application, execute the script. Or they can simply add an entry to a separate journal.

Action List

Warnings: Message Box Notification Sound signal Write to file

Alerts: Email Jabber Event Log

Measures: Run the application Execute the script Restart the service Restart the computer

All actions performed and all changes in observed parameters are continuously recorded in the log, forming a clear picture of the state of the network.

Recording checks in the monitor log

Total Network Monitor 2 monitors all running monitors and records the necessary information about the operation of the checks. Any change in the monitor state is recorded in Monitor log:

Statistics and activity chart

Statistics include startup time and last check selected monitor, the total number and the number of green, red and black states of the monitor. A separate tool can be called activity diagram, which graphically displays the results of checking the selected monitor.

Monitoring actions in the log

TNM records every completed and uncompleted action in Action log, showing the timecode, as well as the name and IP address of the target equipment:

Convenient map of network devices

Build a visual plan for your monitoring project with network maps: Place icons of computers, devices, and servers on an enterprise diagram or world map, and depict the network structure using connections.

Color indication next to each device on the network map allows you to quickly determine their status.