KR101913698B1 - Web sit monitoring apparatus based on external measurement node, web sit monitoring method based on external measurement node - Google Patents

Abstract

A website monitoring apparatus and method are disclosed. The website monitoring apparatus includes: a website monitoring system which determines whether or not a failure is generated by monitoring a server or a website and generate failure phenomenon information and website failure cause information; a server monitoring system which generates server side failure cause information by monitoring server (host) and network equipment constituting the server and the website; and a failure cause analysis and treatment system which inputs the failure phenomenon information, the website failure cause information, and server side failure cause information, determines a failure cause matched to a failure phenomenon, and analyzes failure treatment information about the determined failure cause, thereby effectively maintaining the quality of the website by monitoring the whole section such as an external line, a web error, a web content error, and a system error.

Description

[0001] The present invention relates to an external measurement node-based web site monitoring apparatus, an external measurement node based web site monitoring apparatus, and an external measurement node based web site monitoring apparatus,

The present invention relates to a web site monitoring apparatus and method, and more particularly, to a web site monitoring apparatus and method, which collects fault analysis data and analyzes the cause of the fault by comparing the collected fault analysis data with monitoring results, ≪ / RTI > The present invention also relates to an external measurement node-based website monitoring apparatus and method that enables monitoring of a website from a plurality of external measurement nodes, thereby enabling monitoring of the website monitoring from a user's point of view and maintaining the global quality.

As the service provided by the company is changed to the web environment, the impact of the web service failure on the reliability of the enterprise is increasing. According to statistics, 40% of customers are known to fail if they fail to access web services within 3 seconds.

The cause of this Web service failure occurs not only inside the system but also throughout the service. Even from a system point of view, a normal user is recognized as a fault.

Figure 1 shows the distribution status of causes of Web service failures.

Referring to FIG. 1, a Web service failure on the user's perspective includes a user line failure, a web site failure, a server / network failure (internal system failure), and the like.

The user line failure refers to a failure of the user's external network, which causes a connection failure, a delay phenomenon, and so is recognized as a Web service failure from the user's point of view.

Web site chapter includes Web site loading time delay, image and link error, and is recognized as Web service failure from the user's point of view.

Server / network failures include server and OS, network devices, and are also perceived as Web service failures from the user perspective.

As described with reference to FIG. 1, the causes of web service failure are variously present in a line, an OS, a server, a network, a web program, and the like.

On the other hand, the IT environment is also evolving complexly, such as increasing mobile connectivity and configuring hybrid services.

As a result, system operators are experiencing difficulties in monitoring and responding to websites, which leads to delays in failure recovery and a decrease in reliability.

Statistically, about 80% of Web services operations engineers are engaged in Web site monitoring and recovery. However, as the burden of processing the fault is increased, engineers are avoiding the task of fault handling.

Figure 2 shows examples of website failures.

Referring to FIG. 2, it can be seen that an average recovery time of 531 minutes (8 hours 51 minutes) per web site failure is required. This is because, as described with reference to FIG. 1, the cause of the trouble is complex and difficult to analyze.

This situation increases the burden of the Web service operation engineer, which causes the engineer to avoid the operation task and increases the time spent in the non-creative work such as the disability processing, so that the creative work such as learning new technology and planning Thereby reducing the amount of time spent in the process. As a result, Web site failures are causing the technological competitiveness of companies to deteriorate.

Therefore, it is necessary to solve the problem of web service quickly.

On the other hand, as Korean companies' global service penetration has increased, it has become necessary to monitor the quality of Web site access in the global region.

[Patent Literature]

Patent Document 1; 10-2004-0089174 (published on October 21, 2004); A web content monitoring method, a computer readable recording medium having the web content monitoring method, and a web content monitoring system

Patent Document 2; 10-2015-0049541 (published May 5, 2015); Systems and methods for automating data center failure event management

Patent Document 3; 10-2010-0133168 (Released on December 21, 2010); Monitoring and analysis of application failure in IT service

Patent Document 4; 10-2008-0097254 (November 11, 2008) Disability and Performance Information in Integrated Management System Environment

SUMMARY OF THE INVENTION The present invention has been proposed in order to solve the above-mentioned problems, and it is an object of the present invention to provide a web site monitoring apparatus capable of immediately recognizing and responding to a web service failure.

It is another object of the present invention to provide a method of monitoring a web site that can recognize a web service failure immediately and cope with it.

It is still another object of the present invention to provide a computer-readable recording medium on which a web site monitoring method capable of immediately recognizing and responding to a web service failure is provided.

A web site monitoring apparatus according to the present invention for achieving the above object

1. A web site monitoring apparatus for monitoring a failure of a server and a web site for a web service, analyzing a cause of the failure, and providing a fault prescription,

A web site monitoring system for monitoring a web site constituting the server and a web site to determine whether or not a fault has occurred, and generating a fault phenomenon information and a web fault cause information;

A server monitoring system for monitoring server (host) and network equipment constituting the server and the web site and generating server side failure cause information; And

A failure analysis and prescription system for inputting failure phenomenon information, failure cause information on the web side, cause information on the server side failure, determining a failure cause matched with the failure phenomenon, and analyzing the large prescription information on the determined failure cause;

And a control unit.

Here, the website monitoring system may determine whether a web site has a failure by comparing the measured value obtained by accessing the web site from the external measurement node with a predetermined threshold value.

The external measurement node agent is installed in the external measurement node and accesses the web site to generate a measurement value.

Here, the measurement items of the external measurement node agent include the following.

a. DNS response time, response time

b. Page response time, response time, http status

c. Page loading time

d. Page capacity

e. Page configuration component response time, response time, http status

f. Error on page link

The website monitoring system

1) Availability monitoring

2) Connection, content monitoring

3) DNS monitoring

Here, the external measurement node includes a domestic node and an overseas node.

Here, the domestic nodes are installed for each communication company.

Here, the foreign nodes are installed in each country.

The web service monitoring apparatus according to the present invention enables monitoring of all sections such as an outside line, a web error, a web content error, and a system error, thereby effectively maintaining the quality of a web site.

The web service monitoring apparatus according to the present invention has an effect of enabling quick response to a failure by automating the detection of the cause of the failure and the derivation of the countermeasure by utilizing the knowledge base database.

The web service monitoring apparatus according to the present invention has an effect of providing global service quality by monitoring a web site through a plurality of external measurement nodes at home and abroad.

The web service monitoring apparatus according to the present invention can effectively maintain the quality of a web site by quickly providing a cause analysis and a processing method for a failure that occurs.

Figure 1 shows the distribution status of causes of Web service failures.
FIG. 2 shows examples of website failure response and recovery.
FIG. 3 shows a detailed configuration of a web site monitoring apparatus according to the present invention.
FIG. 4 illustrates an operation of automatically generating monitoring setting information using an agent installed in the server.
Figure 5 schematically illustrates the operation of a website monitoring and analysis system.
Figure 6 shows a portion of the content contained in the knowledge base database.
Figure 7 shows the failure cause analysis and the operation of the prescription system.
8 shows a method of monitoring a website according to the present invention.
9 shows a process of establishing a website-server association.
FIG. 10 shows a web site monitoring process in detail.
FIG. 11 specifically shows a server (host) monitoring process.
Figure 12 shows in detail the cause analysis and prescription process of the website failure.
13 shows an example of grouping of web service units.
FIG. 14 shows a process of comparing a server (host) monitoring result with a knowledge base database as a result of a web site monitoring and providing a failure cause and a response analysis result to a user.
15 shows a method of monitoring a website using a knowledge-based database.

Hereinafter, the configuration and operation of the present invention will be described in detail with reference to the accompanying drawings.

FIG. 3 shows a detailed configuration of a web site monitoring apparatus according to the present invention.

Referring to FIG. 3, a web site monitoring apparatus 100 according to the present invention includes:

A web site monitoring system 104, a server (host) monitoring system 106, a failure cause analysis and prescription system 108, and an external measurement node 114.

The server and web site 102 are company internal IT systems for web services and are monitored by the web site monitoring apparatus according to the present invention.

Reference numeral 110 denotes a user portal, and reference numeral 112 denotes a customer interface monitoring user interface (UI).

The web site monitoring system 104 monitors a web site 102a constituting a server and a web site 102 and is a web site monitoring system that monitors a web site quality of a web site provided by a server and a web site 102, Monitoring and fault monitoring,

1) Measurement of availability

2) Connection, content monitoring

3) DNS monitoring

And so on.

The operation of this website monitoring system 104 is associated with an external measurement node 114.

Specifically, the web site monitoring system 104 performs a spurious monitoring of the web service by comparing the measured value measured when the web site is accessed by the external measurement node 114 with a preset threshold value, .

The external measurement node 114 refers to a site existing outside the server and the web site 102.

The external measurement node 114 is provided with an external measurement node agent for accessing the website and measuring values for various measurement items.

This external measurement node agent may be an external measurement node agent program implemented in the form of a program.

The external measurement node agent may also be implemented in the form of a device.

The present invention is not particularly limited as long as the external measurement node agent is implemented in the form of a program or a device.

The metrics at the external measurement node agent may include:

a. DNS response time, response time

b. Page response time, response time, http status

c. Page loading time

d. Page capacity

e. Page configuration component response time, response time, http status

f. Error on page link

The server monitoring system 106 performs internal IT system resource and failure monitoring of the server and the web site 102,

1) CPU, MEM, DISK monitoring

2) Ping, Process, Log monitoring

3) Network monitoring

And so on.

The server monitoring system 106 compares the measured value measured through the agent installed in the server (host) 102b with a predetermined threshold value to determine whether the server (host) 102b has failed.

The web site monitoring system 104 and the server monitoring system 106 can implement an end-to-end monitoring system.

The server (host) 102b is provided with an agent (server (host) agent) for measuring various measured values.

The server (host) agent may be a server (host) agent program implemented in the form of a program.

The server (host) agent may also be implemented in the form of a device.

The present invention is not particularly limited as long as the server (host) agent is implemented in the form of a program or a device.

The metrics at the server (host) agent may include:

a. CPU, MOM, DISK, Network Usage

b. Existence of set process

c. Whether the keyword of the set Log is found

d. Existence of set port

Meanwhile, a server (host) agent installed in the server (host) 102ba communicates with the server monitoring system 106 to generate monitoring setting information according to the OS, the role of the server, and the service environment of the server. Here, the monitoring setting information includes measurement items measured for monitoring.

4 shows an operation for generating monitoring setting information using a server (host) agent installed in the server.

First, in step S402, a server (host) agent is installed in the server (host) 102b.

Instead of installing a server (host) agent on a network device, it monitors it using Simple Network Management Protocol (SNMP) provided by ordinary network equipment.

In step S404, the server (host) agent grasps the server (host) information and registers the server (host) information in the server monitoring system 106.

For example, the server (host) agent grasps the basic information of the server (host) 102b such as IP of the server (host) 102b, host name, CPU / .

Enter additional information in step S406. Additional information can be entered by the user.

Additional information includes:

a. OS environment of the server

b. Role of the server

c. Service environment of the server

d. Service environment of network device

If the additional information is input, in step S406, the server (host) 102b requests a server (host) monitoring setting template suitable for the server (host) 102b in the knowledge base database 108.

The server (host) monitoring setting template refers to a collection of measurement items for monitoring the server (host) 102b and includes, for example, a monitored log file, a process, a port number, and the like. The measurement items for monitoring the server (host) 102b are closely related to the relationship between the server (host) 102b and the website 102a.

The knowledge base database 108a is provided with a server (host) monitoring setting template according to a representative website-server (host) association relationship. These server (host) monitoring configuration templates are based on real implementation cases in the IT field.

In step S408, server (host) monitoring setting information is automatically registered using the server (host) monitoring setting template transmitted from the knowledge base database.

When the user inputs the role of the server (host) (WEB, WAS, DB) and the service environment (NginX, Tomcat, Mysql etc.) provided for performing the role, the monitoring setting Select a template and use it to automatically register monitoring configuration information.

In step S410, server (host) monitoring is performed by referring to the registered server (host) monitoring setting information.

As described above, the present invention can automatically generate the server (monitoring) setting information only by inputting simple information (OS environment of the server, role of the server, service environment of the server, and service environment of the network equipment) It is possible to greatly reduce human and material resources for

The failure cause analysis and prescription system 108 includes a knowledge base database 108a that performs failure cause analysis and prescription beyond simple failure monitoring.

The failure cause analysis and prescription system 108 includes a knowledge base database 108a, a cause analysis system 108b, and a failure prescription system 108c.

The cause analysis system 108b inputs the failure phenomenon, the cause of the web side failure, and the cause of the server side failure, and analyzes the cause of the failure by referring to the knowledge base database 108a.

Failure phenomena include:

1. Web site not responding: user does not respond to page request

2. Abnormal http status of website: If the user returns an abnormal http status to the page request

3. DNS not responding: DNS does not respond to URL requests.

4. Page Delay: If the entire web page has not been loaded within a given time (usually 10 seconds)

5. Component error: If the component (image, script, etc.) that constitute a web page shows an abnormal status

6. Component Delay: If loading of the component takes longer than usual (typically 10 seconds)

The failure prescription system 108c inputs the analyzed failure cause and outputs the failure prescription by referring to the knowledge base database 108a.

The user portal 110 displays the failure analysis result to the user.

The user portal is a user interface (for example, a web site screen) for displaying contents provided by the service such as monitoring setting, user setting, monitoring result display, and failure analysis result display.

The demander contact person monitoring UI 112 is to refer to the fault analysis result so as to perform a work for solving the cause of the fault.

The demander person is a user who uses the service provided by the web service monitoring apparatus 100 according to the present invention. The user can set monitoring, user setting, monitoring result, and failure analysis result through the demander person monitoring UI 112 .

Figure 5 schematically illustrates the operation of a website monitoring and analysis system.

5, the website monitoring system 104 monitors connection time, availability, DNS response time, web component loading time, and the like as the web site 102a is accessed by the external measurement node 114, , And the failure phenomenon.

To this end, an external measurement node agent is installed in the external measurement nodes 114a to 114n.

A plurality of external measurement nodes 114 may be installed for each country / country, country, and communication company. By monitoring the website 102a through the external measurement node 114 and by monitoring the web site 102a by domestic / international, country, and carrier through a plurality of external measurement nodes 114, End-to-end monitoring can be performed and global quality can be maintained.

The main operations of the website monitoring system 104 are as follows.

1) Website Uptime Diagnosis

2) Diagnosis of Web site connection time by communication company

3) Diagnose website access time by country

4) Web service availability analysis

5) Web service utilization rate analysis

6) DNS response time diagnosis

7) Diagnose web content loading time

8) Web component error diagnosis

9) Web component delay diagnosis

10) Web content capacity change diagnosis (identification such as hacking)

11) Diagnosis by user scenario

12) Setting threshold alarm for each situation

13) Automatic alarm and report function

Figure 6 shows a portion of the content contained in the knowledge base database.

The knowledge base database 108a contains prescriptions that are taken to repair the failure phenomenon, the cause of the failure, and the failure phenomenon. The failure phenomenon can be detected by analyzing the system log generation message. The cause of the disorder is the cause of the disorder, and the prescription is a measure taken to overcome the disorder.

These disability phenomena, causes of failures, and prescriptions are collected and organized on the basis of actual cases in the IT field and recorded in the knowledge base database 108a.

As described above, according to the present invention, the collected data based on actual cases, that is, the failure phenomenon, the cause of the occurrence of the failure phenomenon, and the prescription taken to overcome the failure phenomenon are recorded in the knowledge base database 108c and applied Enabling rapid recognition of the cause of the failure and precise prescription.

Figure 7 shows the failure cause analysis and the operation of the prescription system.

Referring to FIG. 7, the failure cause analysis and prescription system 108 performs failure cause analysis, comparison of failure state measurement values, and failure diagnosis provision.

① Analysis of cause of disability

First, in the failure cause analysis process (S702), the failure phenomenon, the cause of the web side failure, and the cause of the server side failure are input, and the cause of the failure is analyzed by referring to the knowledge base database.

The failure phenomenon can be detected by analyzing the system log generation message.

The cause of the web side failure and the cause of the server side failure are determined by referring to the monitoring results of the web monitoring system and the server monitoring system, respectively.

② Comparison of measured values of failure status

In the failure state measurement value comparison process (S704), a determination is made as to whether a failure has occurred by comparing the measured value with a preset threshold value, and a priority order of the factors causing the failure cause is determined. Here, the threshold value is set to a measurement value that can be determined as a failure.

Fault priorities are determined by rules designed by analyzing various real-world examples of IT.

Specifically, various actual cases are scored for each failure cause, degree of impact on web service, frequency of occurrence, etc., and the result is stored in a knowledge base database. .

③ Providing disability prescription

In the failure prescription providing process (S706), a method for eliminating the failure cause is identified and presented to the user.

8 shows a method of monitoring a website according to the present invention.

In FIG. 8, the server and the web site are internal IT systems for web services, including a server (host), a web site, a network equipment, and the like. The term server (host) means that it contains a host that acts as a server.

In general, a server may include a plurality of hosts, and a host included in one server may be operatively associated with a host included in another server.

The server monitoring process (S802) monitors the internal IT system resources and monitors failures of the server and the web site. That is, the server (host), the network device, and the like are monitored and monitored for failure.

The web site monitoring process (S804) is a process of monitoring a web site constituting a server and a web site, and performs web service quality monitoring and failure monitoring for a user.

The failure cause analysis and prescription process (S810) performs not only simple failure monitoring but also failure cause analysis and prescription. The failure cause analysis and prescription system 108 minimizes the Web service disconnection time by presenting a failure resolution in the shortest time.

9 shows a process of setting up server monitoring information.

In order to make a Web service, an IT system is generally composed of a Web site, a Web server, a WAS server, a DB server, and a network device. By monitoring the status of each Web site and server, we can analyze the cause of the failure through the monitoring measurement result of the server that has a relationship with the Web site.

In step S902, website information is registered, and in step S904, website information is stored.

The website information registered in step S902 is the URL of the web site to be monitored.

In step S906, server (host) information is registered. In step S808, server (host) information is stored.

The server (host) information registered in step S906 includes the following.

a. Server (Host) IP

b. Host classification; Servers, network equipment

c. OS; Window, Ubuntu ,,,

In step S910, website failure analysis information is registered.

In step S912, a web site-server (host) association is established based on the website information and the server (host) information.

The website-server (host) association information registered in step S912 includes a server (host) role and a provision service.

Here, the server (host) role and provision service are classified as follows.

a. Server (host) role; WEB server, WAS server, DB server, network device, etc.

b. Provided services; Apache, Nginx, Mysgl, Jboss ,,,

c. Service environment; The log file location, service name, and port number used by each service.

In step S914, the website-server (host) association is determined and stored. The website-server (host) association information includes information that is understood by the server (host) agent and additional information that is input by the user.

In step S916, the server (host) monitoring setting template is determined by referring to the website-server (host) association information and the knowledge base database 108a.

The server (host) monitoring configuration template is a collection of items for server (host) monitoring. The knowledge base database is provided with a server (host) monitoring setup template according to a representative website-server (host) association.

Web site-server (host) association-specific monitoring configuration templates include:

a. About Process Monitoring Settings by Relationship

b. About logging monitoring settings by relationship

c. About port monitoring settings by relationship

In step S916, a server (host) monitoring setting template to be applied to the measurement target web site is determined from among the server (host) monitoring setting templates according to the stored website-server (host) relationship in step S814.

In step S918, the server (host) monitoring configuration template is verified.

The server (host) monitoring setting template contains the monitoring setting information. In step S918, the server (host) monitoring setting template stores measurement values (for example, log files, processes and ports to be monitored) included in the server To the server (host) agent installed in the server (host).

When the requested measurement value is received, it is regarded that the verification is successful, and the monitoring setting information is registered by applying the server (host) monitoring setting template in step S92.

Incorrect user input If a measurement is not received due to, for example, a server (host) role or an incorrect input to the service environment, verification will fail and you will be asked to reset the server (host) monitoring configuration template.

If the verification fails, the server (host) monitoring configuration template is modified in step S820 and the process returns to step S818.

The modification in step S820 can be performed manually. The role of the server (host) entered by the user and the monitoring setting values that are deemed appropriate for the service environment are contained in the server (host) monitoring setting template. If the set value does not match the actual environment, that is, the role of the server (host) input by the user and the service environment, the user or the manager (the person who manages the apparatus performing the web service monitoring method according to the present invention) Can be modified.

If the verification is successful, the setting operation for monitoring the server (host) is completed in step S922.

Table 1 shows an example of a server (host) monitoring setup template stored in the knowledge base database.

Item Contents OS environment  OS environment of server (host) such as Windows, Ubuntu, Redhat, etc. Association  Web server -Apache, Web server -nginx, WAS server -tomcat, DB server -myql, Network equipment, etc. Relationship with website and contents of service Process settings  Process name and number of processors to monitor, such as Apache, httpd, mysqld Log setting  System Forger, Tomcat error log, etc. Log file path by monitoring target log and keywords to be exported Port setting  http port, mysql communication port, etc. Monitored port Other settings  Settings for other required items, such as resource usage

WAS stands for Web Application Server.

The web site monitoring method according to the present invention can automatically set server (host) monitoring setting information according to the server (OS, role, and service environment of the host).

FIG. 10 shows a web site monitoring process in detail.

In step S1002, website monitoring setting information is registered, and in step S1004, website monitoring setting information is stored.

The website monitoring configuration information may include the following items.

a. URL of the website to be measured

b. Metrics

c. Threshold for measured value

d. Measurement cycle

The website monitoring setting information can be inputted through the user portal, the demander person monitoring UI, etc. in the course of registering the web site monitoring setting.

In step S1006, the external measurement node monitors the measurement target web site. Specifically, measurement values are obtained by measuring various kinds of measurement items that occur when an external measurement node accesses a measurement target web site.

In step S1008, the web site monitoring result is stored.

The metrics may include:

a. DNS response time, response time

b. Page response time, response time, http status

c. Page loading time

d. Page capacity

e. Page configuration component response time, response time, http status

f. Error on page link

In step S1010, the measurement value is compared with the threshold value to determine whether the measurement target web site has failed.

In step S1012, the monitoring result is displayed to the user according to the failure.

In step S1014, an alarm is generated to the user by a method such as Mobile App Push, Email, SMS, etc. for the determined failure.

FIG. 11 specifically shows a server (host) monitoring process.

In step S1102, an agent for measurement is installed on the server (host), monitoring setting information for server (host) monitoring is registered, and server monitoring setting information is stored in step S1104.

The server (host) monitoring setting information may include the following.

a. IP of the target server (host)

b. Threshold for resource usage

c. Process monitoring settings

d. Log monitoring settings

e. Port monitoring settings

As described with reference to FIG. 9, the server (host) monitoring setting information is automatically set with reference to the web site-server (host) association information and the server (host) monitoring setting template stored in the knowledge base database.

In step S1106, measurement results are collected.

Specifically, when the agent installed in the server (host) generates measurement values for various measurement items, the measurement values generated in step S1006 are collected.

In step S1108, the server (host) monitoring result is stored.

The metrics may include:

a. CPU, MOM, DISK, Network Usage

b. Existence of set process

c. Whether the keyword of the set Log is found

d. Existence of set port

In step S1110, it is determined whether the server (host) has failed by comparing the measured value and the threshold value.

In step S1112, the monitoring result is displayed to the user depending on the failure.

In step S1114, an alarm is generated to the user by a method such as Mobile App Push, Email, or SMS for the determined failure.

Figure 12 shows in detail the cause analysis and prescription process of the website failure.

In step S1202, the website-server (host) association information is stored.

In step S1304, the web site monitoring result is stored.

In step S1206, the server (host) monitoring result is stored.

In step S1208, the website-server (host) measurement result is matched.

Among the measurement results of a plurality of Web sites and measurement results of a plurality of servers (hosts), the measurement results of the related websites and the measurement results of the servers (hosts) based on the association information between the website and the server (host) Match.

In step S1210, the cause of the failure of the website is determined by referring to the knowledge base database.

The knowledge base database stores the cause of failure, countermeasures, and priorities for Web site - server (host) association and environment - specific measurement results.

In step S1212, the priority of the failure cause is determined by referring to the knowledge base database.

In step S1214, we determine the countermeasures for each failure cause by referring to the knowledge base database.

S1216 stores the result of analyzing the cause of the website failure, and S1218 displays the result of analyzing the cause of the website failure.

In S1218, the causes of failures can be sorted according to their priority, and countermeasures for each cause of failures can be indicated and indicated.

Table 2 shows examples of failure reasons, countermeasures, and priorities stored in the knowledge base database.

Configuration item Contents OS environment OS environment of host such as Windows, Ubuntu, Redhat Association Web server -Apache, Web server -nginx, WAS server -tomcat, DB server -myql, Network equipment, etc. Relationship with website and contents of service Metrics Items of comparative measurement data for determining cause of failure such as process, port, and log monitoring Measurement result A measurement value that can be judged as a cause of failure for a measurement item Failure cause The cause of the problem that can be judged when the measurement result is matched to the measurement item Countermeasures What to do about the cause of the failure Priority In the case of a disability situation,

The present invention enables systematic management and monitoring of a web service configuration host through grouping of web service units.

13 shows an example of grouping of web service units.

13, the service environment between the web site and the server (host) is set for each server (host), and the web service unit grouping can be performed by synthesizing and analyzing them.

The association between the server (host) and the web service that is a unit of grouping is directly set through the monitoring UI of the demander contact person.

Generally, a number of hosers, which serve as web servers, WAS servers, DB servers, and network equipment, gather to provide a single web service.

The present invention can analyze the monitoring result of various servers (hosts) constituting the web service together with the result of the monitoring of the web site, thereby analyzing the cause of the failure for one web service.

In order to analyze the failure cause of the web service unit, a grouping is performed by setting a connection line between a web site and various servers (hosts) for each web service.

The right picture of FIG. 13 shows the result of the web service unit grouping named project1.

Through the grouping of Web service units, it is possible to instantaneously grasp the obstacle section when a charity of a Web service occurs, thereby enabling analysis of the cause of the obstacle and minimization of the response time.

The web site monitoring method according to the present invention has an advantage that accurate analysis can be performed by comparing the measurement result with a knowledge base database to analyze the cause of the failure.

FIG. 14 shows a process of comparing a server (host) monitoring result with a knowledge base database as a result of a web site monitoring and providing a failure cause and a response analysis result to a user.

Referring to FIG. 14, Web site-server association, environment setting values, website monitoring results, and server (host) measurement results are provided in a knowledge base database.

The knowledge base database stores various case information.

The knowledge base database compares the web site-server association, environment setting value, website monitoring result, server (host) measurement result with various failure case information, and selects the similarity failure case.

Select the cause of failure and the countermeasure for the selected failure case, and present the failure cause and the analysis result to the user according to the priority of the failure cause.

As described above, the web site monitoring method according to the present invention has the effect of contributing to the quick failure recovery by providing the failure cause and the countermeasure to the user according to the failure priority.

The web site monitoring method according to the present invention compares the monitoring result of a web site and a server (host) with a knowledge base database to provide a failure cause and a result of the analysis.

15 shows a method of monitoring a website using a knowledge-based database.

Referring to FIG. 15, the knowledge base database includes Web site-server (host) association environment case information, web site failure case information, server (host) failure case information, failure cause of each failure case, .

Web site monitoring measures and server (host) monitoring measurements are compared with knowledge base data to derive failure cases, and the causes and countermeasures of failure cases are derived.

The cause of the failure case and the countermeasure are reported to the user.

As described above, the web site monitoring method according to the present invention provides a failure site and a response analysis result by comparing the monitoring results of a web site and a server (host) with a knowledge base database, It is possible to minimize the failure cause and the response time.

A web site monitoring method according to the present invention requests a web page from a web site through an external measurement node set outside the web site, and analyzes the response to the request to monitor whether the web site has a failure.

Here, we have a domestic measurement node to monitor the domestic web service situation and an overseas measurement node for each overseas region in order to measure the situation of the website by the overseas region. In the present invention, the external measurement nodes installed in the country and abroad are expressed as global measurement nodes.

100 ... Website monitoring device
102 ... Servers and Websites 104 ... Website Monitoring System
106 ... server (host) monitoring system 108 ... failure cause analysis and prescription system
110 ... user portal 112 ... customer contact person monitoring UI
114 ... external measurement node

Claims (7)

1. A web site monitoring apparatus for monitoring a failure of a server and a web site for a web service, analyzing a cause of the failure, and providing a fault prescription,
A web site monitoring system for monitoring the server and the web site to determine whether or not a fault has occurred, and generating a fault phenomenon information and a web fault cause information;
A server monitoring system for monitoring server (host) and network equipment constituting the server and the web site and generating server side failure cause information; And
An obstacle analysis system and a prescription system for analyzing obstacle prescription for the determined obstacle cause by judging the cause of the obstacle matched to the obstacle phenomenon and inputting the obstacle cause information of the web side and the cause information of the obstacle side of the server and,
The server monitoring system generates server monitoring setting information using a server agent installed in the server, performs server monitoring based on the server monitoring setting information,
Wherein the server monitoring setting information is registered based on a server monitoring setting template which is an aggregate of measurement items for monitoring the server based on actual implementation cases according to an association between the server and the website,
The failure cause analysis and prescription system comprises:
A knowledge base database containing a failure symptom, a cause of a failure, and a failure prescription taken to recover a failure phenomenon, and providing the server monitoring setup template to the server monitoring system;
A causal analysis system for analyzing a cause of failure, a cause of web side failure, a cause of server side failure, and a cause of failure by referring to the knowledge base database; And
And a failure prescription system for inputting a failure cause analyzed by the cause analysis system and outputting a failure prescription corresponding to the failure cause by referring to the knowledge base database,
The server monitoring system includes:
If the service environment for performing the role and role of the server is input by the user, the monitoring setting template matching the input role and the service environment is selected and the monitoring setting information is registered using the selected monitoring setting template
Website monitoring device.
delete delete delete delete delete delete

Images