WO2016017208A1 - 監視システム、監視装置、および検査装置 - Google Patents
監視システム、監視装置、および検査装置 Download PDFInfo
- Publication number
- WO2016017208A1 WO2016017208A1 PCT/JP2015/058067 JP2015058067W WO2016017208A1 WO 2016017208 A1 WO2016017208 A1 WO 2016017208A1 JP 2015058067 W JP2015058067 W JP 2015058067W WO 2016017208 A1 WO2016017208 A1 WO 2016017208A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- message
- node
- monitoring
- inspection
- messages
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
- G06F11/0709—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0751—Error or fault detection not based on redundancy
- G06F11/0754—Error or fault detection not based on redundancy by exceeding limits
- G06F11/076—Error or fault detection not based on redundancy by exceeding limits by exceeding a count or rate limit, e.g. word- or bit count limit
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0787—Storage of error reports, e.g. persistent data storage, storage using memory protection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3452—Performance evaluation by statistical analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3495—Performance evaluation by tracing or monitoring for systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/50—Testing arrangements
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2294—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by remote test
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/81—Threshold
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/875—Monitoring of systems including the internet
Definitions
- the disclosed subject matter relates to a monitoring system, a monitoring apparatus, and an inspection apparatus that inspects the monitoring target system.
- An example of a network system is a cellular phone packet switching system.
- the packet switching system is composed of a group of network nodes (hereinafter “nodes”) which are devices having various functions. If a failure or congestion occurs in these nodes, a state where a sufficient communication service cannot be provided to the end user, that is, a communication failure occurs. Therefore, it is necessary to detect such a network system communication failure early.
- a single or multiple fixed values are used as threshold values for performance information of the server group to be monitored, for example, CPU usage rate, and an abnormality is detected when the value is exceeded.
- Such a monitoring method is suitable for a system mainly composed of a general-purpose PC server because of easy installation of monitoring software and customization of monitoring settings.
- many network nodes are implemented as dedicated devices, and internal data such as performance information and logs necessary for monitoring that the node has may not be available. Therefore, as a failure detection method for network systems, a technology that detects communication errors between nodes by measuring packets flowing through the network or acquiring information about communication from network devices such as network switches and analyzing them. Is used.
- Patent Document 1 As a conventional technique for monitoring a network system, there is a technique disclosed in Patent Document 1 below.
- Patent Document 1 is a technique that is robust to time fluctuations of observed values or severe correlations, and considers the interdependence of multiple observation points in the runtime environment.
- This is an anomaly detection system that automatically detects failures centered on service stoppage in the application layer.
- the abnormality detection system includes an agent device that records a transaction, which is a service process, in each computer in a computer system that forms a network with a plurality of computers in association with the service.
- each agent device transmits a transaction to the abnormality monitoring server, and the abnormality monitoring server collects the recorded transaction from the agent device.
- Each agent device outputs a node correlation matrix from the collected transaction, and calculates an activity vector by solving an eigen equation of the node correlation matrix. Then, each agent device calculates the outlier degree of the activity vector from the probability density that estimates the probability that this activity vector will occur from the calculated activity vector, so that each of the plurality of computers is related to each other. However, it automatically detects the failure of a program that runs.
- What is disclosed is a technology that suppresses false detection of a failure or non-failure without depending on the number of nodes or the configuration of the nodes.
- One aspect disclosed is an inspection apparatus that inspects a message group that circulates in a monitoring target system that has a plurality of nodes and can communicate between the plurality of nodes, and uses the inspection result from the inspection apparatus, And a monitoring device that monitors the monitoring target system.
- the monitoring device uses a test result received from the test device to count the number of messages for each type of message transmitted / received at the node, and the message for which the number of messages has been tabulated by the count processing For each of the messages sent and received by the monitored system, a starting message that is a starting point, and an occurrence that occurs in the monitored system when the starting message is given to any one of the plurality of nodes Analyzing the relationship between the origin message and the generated message based on the classification process for classifying the message into one of the messages, the number of messages of the origin message classified by the classification process, and the number of messages of the generated message The origin message and the occurrence message And analysis processing for creating a matrix that indicates the relationship between di, when the value of the elements in the matrix is out of the normal range, executes a failure and determining the detection process of the monitoring target system.
- the element value indicates that when an origin message is input to a certain node, an occurrence message has occurred in another node.
- the value of the element is out of the normal range, the value of the element indicates that there is a communication failure due to a software failure or hardware failure such as mass message discard, mass duplication, and mass retransmission. .
- FIG. 10 is a flowchart illustrating a detailed processing procedure example of the abnormality detection processing (step S906) illustrated in FIG. 9.
- FIG. 10 is a flowchart illustrating an example of an in-detail process procedure of the abnormal part specifying process (step S907) illustrated in FIG. 9;
- FIG. 10 is a flowchart showing a detailed processing procedure example of the measurement control process (step S908) shown in FIG. 9.
- This embodiment provides a failure detection method that does not depend on the number of nodes in the network system or the node configuration. As a result, even if the number of nodes and the configuration of the node fluctuate, it is not erroneously detected that there is a failure for a node that is not originally faulty, and it is not erroneously detected that there is no failure for a faulty node. Can be achieved. As the number of nodes increases, the node correlation matrix increases in proportion to the increase in the number of nodes, and the amount of calculation increases. When the amount of calculation increases, it takes time to detect a failure. In this embodiment, since it does not depend on the number of nodes, early detection of a failure can be achieved by suppressing an increase in matrix calculation. Examples will be described below.
- FIG. 1 is an explanatory diagram illustrating a modeling example of a communication state.
- the network system 100 includes a plurality of nodes (N5 in FIG. 1 as an example) Na to Ne (hereinafter collectively referred to as node N).
- the node N is a communication device that is communicably connected to another node N.
- the node Na is eNB (evolved Node B)
- the node Nb is MME (Mobility Management Entity)
- the node Nc is The HSS (Home Subscriber Server)
- the node Nd is an SGW (Serving Gateway)
- the node Ne is a PGW (Packet Data Network) PGW.
- the present embodiment can be applied to a sensor network system as the network system 100 to be monitored.
- the network system 100 includes a sensor node, a route node, and a gateway node.
- the sensor node is a node that measures, for example, the temperature of the observation target in accordance with a command from the server.
- the root node is a node that transfers observation data from the sensor node and transfers a command from the server.
- the gateway node transfers a command from the server to the root node, and transfers observation data transferred from the root node to the server.
- Modeling the sequence of traffic flowing in the network system 100 is as follows.
- the number of first messages x1 to xm of m (m is an integer of 1 or more) sequences 1 to m is a column vector x.
- Elements e (x1) to e (xm) of the column vector x are the numbers of the first messages x1 to xm of the sequences 1 to m.
- the first messages x1 to xm of the sequences 1 to m are used, but the message is not limited to the first message as long as the message type is specified.
- the number of subsequent messages y1 to yn generated by using the first message in the network system 100 as a trigger is assumed to be a row vector y.
- Elements e (y1) to e (yn) of the row vector y are the numbers of messages y1 to yn that are generated in a chain when the first messages x1 to xm of the sequences 1 to m are input.
- the failure of the network system 100 is detected by monitoring the elements of the transformation matrix A that converts the column vector x to the row vector y.
- the transformation matrix A is calculated by the product of the inverse matrix x ⁇ ⁇ 1 ⁇ of the row vector y and the column vector x. Since the transformation matrix A does not depend on the number of nodes in the system or the configuration of the nodes, even if there is a change in the number of nodes or the configuration of the nodes, no false detection of failure or non-failure occurs. Further, even if the number of nodes is increased, the number of types of messages circulating in the network system 100 does not change, so the number of elements of the transformation matrix A does not increase. Therefore, there is no increase in the amount of calculation when calculating the transformation matrix A, and it is possible to detect a failure early.
- FIG. 2 is an explanatory diagram showing an example of the relationship between the sequence of traffic flowing in the network system 100 and the conversion matrix A.
- the subsequent messages y1 to y3 are sequentially generated starting from the message x1 from the node Na and output to the subsequent node, and the last message y3 is input to the node Na.
- the subsequent messages y4 to y7 are sequentially generated starting from the message x2 from the node Nb and output to the subsequent node, and the last message y7 is input to the node Nd.
- subsequent messages y8 are sequentially generated starting from the message x3 from the node Ne and input to the node Ne.
- the node Na which is an eNB
- receives “Attach Request” as an initial message from the user terminal the node Na is an MME with “Attach Request” as the first message x1 of a certain sequence. Transfer to node Nb.
- the node Nb When the message x1 is input, the node Nb generates “Authentication Information Request” as the subsequent message y1 and transmits it to the node Nc which is the HSS.
- the node Nc When the message y1 is input, the node Nc generates “Authentication Information Answer” as the subsequent message y2, and transmits it to the node Nb that is the MME.
- the node Nb When the message y2 is input, the node Nb generates an “Authentication Request” as a subsequent message y3 and transmits it to the node Na that is an eNB. Therefore, when this sequence occurs, the number of messages x1, y1 to y3 is counted by one.
- the sequence 2 starting from the message from the node Nb as the MME has been simplified for the sake of explanation, but another example of the sequence 2 is a Detach sequence.
- the Detach Request which is the first message
- the UE User Equipment
- the Delete Session Request is transmitted to the node Nd that is the SGW.
- the node Nd Upon receiving the Delete Session Request, the node Nd generates a Delete Session Request and transmits it to the node Ne, which is a PGW, and the node Ne returns a Delete Session Response to the node Nd.
- the node Nd Upon receiving the Delete Session Response, the node Nd generates a Delete Session Response and transmits it to the node Nb.
- the node Nb further receives a Receive Accept from the UE via the node Na, the node Nb generates a UE Context Release Command in the node Na and transmits it to the node Na.
- the node Na transmits the UE Context Release Complete to the node Nb, and the node Nb receives the UE Context Release Complete. This completes the Detach sequence.
- the number of columns of the transformation matrix A is the number of messages x1 to x3 as a starting point, that is, the number of sequences, and the number of rows of the transformation matrix A is the number of subsequent generated messages y1 to y8.
- An element having a value of “0” in the transformation matrix A indicates that no message is flowing. For example, when attention is paid to the value “0” of the element where x2 and y1 intersect, it is not specified from the transformation matrix A, but in sequence 2, the message y1 is not generated even if the message x2 is input. means.
- an allowable range of the element value v for example, a range where v is 0.5 or more and 1.5 or less
- an average value of time-series element values in the same message is a normal value
- an allowable range of the average value av (for example, the average value av is (av ⁇ (th) and a range of (av + th) or less) is set in advance, and the element value v may be normal when the value is within the allowable range (th is a threshold value).
- FIG. 3 is a block diagram illustrating a system configuration example of the monitoring system according to the present embodiment.
- the monitoring system 300 is a system that detects a communication failure in the network system 100 by observing communication traffic in the network system 100 to be monitored, creating a conversion matrix A, and monitoring the conversion matrix.
- the network system 100 to be monitored includes a node group Ns that is a plurality of nodes Na to Ne, and a system management server 101 that manages the node group Ns. There may be a plurality of nodes Na to Ne.
- the node N communicates with other nodes N via the network 11.
- the network 11 is a computer network such as a LAN (Local Area Network). A wired LAN is generally used, but a wireless LAN may be used. Moreover, you may go through WAN (Wide Area Network).
- the network system 100 may also include one or more network TAP devices 12a to 12d (hereinafter collectively referred to as network TAP device 12).
- the network TAP device 12 duplicates a packet (or frame) transmitted by the network 11, and passes the duplicate packet (or duplicate frame) via the TAP network 13 to the inspection devices 30a and 30b (hereinafter collectively referred to as It is a device that transmits to the inspection device 30).
- the TAP network 13 may use a general LAN cable.
- One or more inspection devices 30 may be provided.
- the network TAP device 12 may be built in the inspection device 21.
- the network TAP device 12 may be incorporated as a function of the node N.
- the network TAP device 12 may be incorporated as a function of a network device such as a router or a network switch.
- the communication traffic transmitted / received between the nodes N is composed of, for example, packets to which a control protocol for controlling each node N is applied.
- An application protocol represented by HTTP (Hypertext Transfer Protocol) may be used.
- the message corresponds to a data unit at the application level in communication traffic transmitted and received between the nodes N.
- a message that is a starting point set in advance among traffic circulating in the network system 100 is set as a starting point message.
- the origin message is the first message in the sequence.
- the messages x1 to x3 shown in FIG. 2 are origin messages.
- a message generated from the node N that has received the origin message is defined as an occurrence message.
- a message generated from the node N that has received the generated message is also referred to as an generated message.
- the messages y1 to y8 shown in FIG. 2 are generated messages.
- each message has a request command as the message type.
- request commands are different, they are classified into different message types.
- a request for connection to the network system 100 ATTACH REQUEST
- a service request SEQUICE REQUEST
- the messages x1 to x3 and y1 to y8 in FIG. 2 are different message types, the number of messages is counted independently.
- the monitoring system 300 includes at least one inspection device 30 and one monitoring device 301.
- the inspection device 30 is a device that monitors the network 11 and inspects messages transmitted and received by the node N.
- the inspection device 30 includes a receiving unit 31, an inspection unit 32, and an inspection control unit 33.
- the receiving unit 31 receives a duplicate packet from the network TAP device 12.
- the inspection unit 32 inspects the content of the duplicate packet and transmits a traffic report including the inspection result to the monitoring device 301.
- the inspection control unit 33 controls a traffic report transmission interval and inspection items in accordance with a control instruction (change instruction or return instruction) from the monitoring apparatus 301.
- the traffic report 34 from the inspection unit 32 includes the measurement date and time and the inspection result obtained by analyzing the content of the duplicate packet for the inspection item.
- the measurement date and time is the date and time when the inspection item was measured. Examples of the inspection item include a protocol name, a message type, a destination IP address, a transmission source IP address, and a communication data amount.
- the monitoring device 301 is a device that receives a traffic report from the inspection device 30 and detects an abnormality in the communication state of the network system 100 using an inspection result included in the traffic report.
- the monitoring device 301 includes a counting unit 302, a creation unit 303, an analysis unit 304, a detection unit 305, a classification unit 306, a specifying unit 307, a measurement control unit 308, traffic statistical information 311, and traffic statistics time. It includes sequence information 312, inter-traffic relationship structure information 313, traffic classification setting information 314, measurement setting information 315, and measurement control information 316.
- the totaling unit 302 receives the traffic report 34 from the inspection device 30 and totals the traffic statistics for each message type from the inspection result included in the traffic report 34 every predetermined total unit time.
- the information 311 is stored.
- the traffic statistic is the number of messages for each message type within the total unit time.
- the traffic statistical information 311 is an area for storing a traffic volume total result for each message type of each message of the message group that is communication traffic. For example, information that the number of messages of the message type “x1” is “938” in a certain total unit time is stored.
- the creation unit 303 reads out the traffic statistical information 311 every predetermined unit time, creates time series data of the traffic statistical information 311, and stores it in the traffic statistical time series information 312.
- FIG. 4 is an explanatory diagram showing an example of the traffic statistics time series information 312.
- the traffic statistics time-series information 312 includes measurement date / time information 401, origin message type information 402, and occurrence message type information 403.
- the measurement date / time information 401 is information on the measurement date / time obtained by dividing the measurement date / time included in the traffic report 34 for each predetermined total unit time. For example, when the predetermined counting unit time is 1 minute, the counting unit 302 measures the measurement described in the traffic report 34 in the entry whose measurement date / time information 401 is “2014/5/15 10:30”. The number of messages whose date is from “2014/5/15/15 10:30: 00” to “2014/5/15 10:30:59” is stored in the traffic statistics information 311 for each message.
- the origin message type information 402 is an area in which the message type described in the traffic report 34 stores the number of messages of the message type classified as the origin message for each message.
- the generated message type information 403 is an area in which the message type described in the traffic report 34 stores the number of messages of the message type classified into the generated message for each message.
- the entries may be deleted from the oldest entry when updated by the creation unit 303.
- the analysis unit 304 reads the traffic statistics time-series data from the traffic statistics time-series information 312 for each predetermined unit time, and analyzes the relationship between the origin message and the generated message.
- the traffic relationship structure data is created and stored in the traffic relationship structure information 313.
- the traffic relationship structure data is the conversion matrix A described above.
- FIG. 5 is an explanatory diagram showing an example of the traffic relationship structure information 313.
- the inter-traffic relationship structure information 313 is inter-traffic relationship structure data, that is, time series data of the conversion matrix A described above. Specifically, for example, taking the measurement date and time T1 as an example, the element columns 511 to 513 become the column vectors 511 to 513 of the transformation matrix A as they are.
- the detection unit 305 compares the current traffic relationship structure data with the past traffic relationship structure data, and detects that there is a change exceeding a predetermined amount, thereby detecting the network system. 100 detects that an abnormality has occurred in the communication state. Then, the detection unit 305 transmits an abnormality detection notification 350 to the system management server 101.
- the classification unit 306 refers to the traffic classification setting information 314 and classifies the message as either the origin message or the generated message.
- the traffic classification setting information 314 is setting information indicating whether each message type corresponds to an origin message or an occurrence message.
- the traffic classification setting information 314 is set in advance by a system administrator or the like.
- the traffic classification setting information 314 is, for example, a setting that a connection request (ATTACH REQUEST) to the network system 100 is a starting point message.
- the IP address range of the external device of the network system 100 may be set in the traffic classification setting information 314. If the source IP address of the message included in the traffic report 34 is within the IP address range specified in the traffic classification setting information 314, the traffic classification processing unit 225 classifies the message as a starting message.
- the classification unit 306 and the traffic classification setting information 314 may be provided in the inspection device 30.
- the traffic report 34 includes the message type classified by the classification unit 306 for each message.
- the specifying unit 307 specifies an abnormality occurrence location.
- the identifying unit 307 identifies the node type of the node where the abnormality has occurred, using the measurement setting information 315 when detecting an abnormality in the communication state of the network system 100. Then, the specifying unit 307 transmits an abnormality detection notification 370 including the node type of the node where the abnormality has occurred to the system management server 101.
- FIG. 6 is an explanatory diagram showing an example of the measurement setting information 315.
- the measurement setting information 315 includes message type information 601, node type information 602, and inspection device information 603.
- the measurement setting information 315 is information set in advance by a system administrator or the like.
- Message type information 601 stores a message type.
- the node type information 602 stores the node type of the node N that processes messages of the message type of the same entry.
- the inspection device information 603 stores identification information that uniquely specifies the inspection device 30 that receives a duplicate message from the node N specified by the node type of the same entry. Thereby, the specifying unit 307 can specify the node type and the inspection apparatus 30 from the message type of the message detected as abnormal by the detecting unit 305 with reference to the measurement setting information 315.
- the measurement control unit 308 controls the inspection apparatus 30. Specifically, the measurement control unit 308 performs control so that the measurement performance of the inspection apparatus 30 increases when the detection unit 305 detects an abnormality in the communication state of the network system 100. Specifically, for example, the measurement control unit 308 shortens the transmission interval of the traffic report 34. When the detection unit 305 detects that the communication state is normal, the measurement control unit 308 returns the measurement performance of the inspection apparatus 30 to the original state before the increase.
- FIG. 7 is an explanatory diagram showing an example of the measurement control information 316.
- the measurement control information 316 includes message type information 701, inspection apparatus information 702, and control content information 703.
- the measurement control information 316 is information set in advance by a system administrator or the like.
- Message type information 701 stores a message type.
- the inspection device information 702 stores identification information that uniquely identifies the inspection device 30.
- the control content information 703 stores the control content of the inspection apparatus 30 specified by the measurement control information 316 of the same entry.
- the measurement control unit 308 reads the control content from the measurement control information 316 and transmits a control instruction 380 that is a message including the read control content to the inspection device 30 specified by the specifying unit 307.
- the control instruction 380 includes, for example, a change instruction that shortens the transmission interval of the traffic report 34 and a return instruction that restores the shortened transmission interval. By receiving the control instruction 380, the inspection device 30 performs processing according to the control content.
- FIG. 8 is a block diagram illustrating a hardware configuration example of the inspection device 30 and the monitoring device 301 (hereinafter, device 800).
- the device 800 includes a processor 801, a main storage device 802, an auxiliary storage device 803, a network interface device 804 such as a NIC (Network Interface Card) for connection to the network 11, an input device 805 such as a keyboard and a mouse, and an output such as a display.
- a device 806 and an internal communication line 807 such as a bus for connecting the devices are provided.
- the device 800 is realized by, for example, a general computer.
- the traffic statistical information 311 can be realized by using a partial area of the main storage device 802. Further, the device 800 loads various programs stored in the auxiliary storage devices 803 to the main storage device 802 and executes them by the processor 801, and connects to the network 11 using the network interface device 804 as necessary. Then, network communication with other devices is performed, or packets from the network TAP device 12 are received.
- FIG. 9 is a flowchart illustrating an example of a monitoring process procedure by the monitoring apparatus 301.
- the monitoring device 301 executes a traffic statistics totaling process by the totaling unit 302 (step S901).
- the aggregation unit 302 receives the traffic report 34 from the inspection device 30 and acquires inspection results such as inspection items and measurement date / time included in the traffic report 34. And total part 302 counts the number of messages for every message type.
- the monitoring apparatus 301 refers to the traffic classification setting information 314 by the classification unit 306 and executes a classification process for classifying the message into either the origin message or the generated message (step S902). Specifically, the classification unit 306 searches the traffic classification setting information 314 using the message type as a search key, and acquires information indicating either the origin message or the generated message that is the classification result. Then, the classifying unit 306 adds the acquired classification result to the traffic statistical information 311. For example, when the message type “x1” having the number of messages “938” is classified as the starting message, the classifying unit 306 sets the message type “x1” and the number of messages to “938” and “starting message”. The information is added to the traffic statistics information 311 in association.
- the classification unit 306 when the classification unit 306 is provided in the inspection apparatus 30, the classification process (step S902) is not executed. In this case, the classification unit 306 adds the classification result included in the traffic report 34 to the traffic statistical information 311.
- the monitoring apparatus 301 uses the creation unit 303 to execute a traffic statistics time series creation process (step S903). Specifically, the creation unit 303 reads the traffic statistical information 311 at a constant time interval and creates a new entry in the traffic statistical time series information 312. Then, the creation unit 303 adds the statistical value for each message type to the new entry of the traffic statistical time series information 312.
- the monitoring apparatus 301 determines whether or not the traffic relationship structure analysis is possible by the analysis unit 304 (step S904). Specifically, the analysis unit 304 determines whether or not the traffic statistics time-series information 312 stores the number of entries necessary for analyzing the traffic relationship structure. For example, the analysis unit 304 determines whether or not the number of entries of the traffic statistical time series information 312 is accumulated more than the number of message types classified as the origin message. If it is not stored, it is not possible to analyze (step S904: No), and the monitoring process is terminated.
- step S904 if it is accumulated, it can be analyzed (step S904: Yes), so the monitoring apparatus 301 uses the analysis unit 304 to execute an inter-traffic relationship structure analysis process (step S905). Specifically, for example, the analysis unit 304 acquires an entry of the traffic statistical time series information 312 in which the conversion matrix A has not been created, and creates the conversion matrix A. The analysis unit 304 stores the traffic relationship structure data, which is the created conversion matrix A, as a new entry of the traffic relationship structure information 313.
- the monitoring device 301 executes an abnormality detection process (step S906), an abnormal part specifying process (step S907), and a measurement control process (step S908).
- an abnormality detection process step S906
- an abnormal part specifying process step S907
- a measurement control process step S908
- FIG. 10 is a flowchart showing a detailed processing procedure example of the abnormality detection processing (step S906) shown in FIG.
- the monitoring apparatus 301 uses the detection unit 305 to refer to the traffic relationship structure information 313 to determine whether each element value in the traffic relationship structure information 313 is within a normal range (step S1001).
- the detection unit 305 calculates an average value of past element values for a predetermined period for each message type, and whether or not the element value of the new entry exceeds the average value ⁇ threshold value. To determine whether or not it is within the normal range. If all the values of the elements of the new entry are within the normal range (step S1001: Yes), the abnormality detection process (step S906) is terminated because of normality, and the process proceeds to step S907.
- the monitoring apparatus 301 uses the detection unit 305 to determine whether the element value outside the normal range is noise. Judgment is made (step S1002). For example, if the noise does not exceed the threshold value th continuously for a certain period of time until it exceeds the threshold th, the detection unit 305 determines that the value of the element outside the normal range is noise. In addition, when the average value of the element values in a certain time until the threshold value th is exceeded does not exceed the threshold value th, the detection unit 305 may determine that the value of the element outside the normal range is noise.
- noise generation is an interruption of communication due to switching hub system switching. For example, if communication is momentarily interrupted but the communication state recovers within a certain time, it can be determined that the communication state of the network system 100 is normal although temporary noise has occurred.
- step S1002 When the value of the element outside the normal range is noise (step S1002: Yes), the monitoring apparatus 301 ends the abnormality detection process (step S906) because it is normal, and proceeds to step S907. .
- the detection unit 305 may transmit a warning notification that the network system 100 is in a noise generation state to the system management server 101.
- step S1002: No when the value of the element outside the normal range is not noise (step S1002: No), the detection unit 305 determines that there is an abnormality and notifies the system management server of an abnormality detection notification (step S1003). Thereby, the abnormality detection process (step S906) is terminated, and the process proceeds to step S907.
- FIG. 11 is a flowchart showing an example of a detailed in-process procedure of the abnormal part specifying process (step S907) shown in FIG.
- the monitoring apparatus 301 searches the measurement setting information 315 by using the message type that is the value of the element outside the normal range as the search key by the specifying unit 307, and the node type information 602 and the inspection apparatus information 603 of the matched entry Information for specifying the type and the inspection apparatus is acquired (step S1101).
- the monitoring device 301 notifies the system management server 101 of an abnormal location notification by using the specifying unit 307 as information indicating the acquired node type and inspection device as an abnormal location (step S1102).
- the abnormal part specifying process step S907) is ended, and the process proceeds to step S908.
- FIG. 12 is a flowchart showing a detailed processing procedure example of the measurement control process (step S908) shown in FIG.
- the monitoring device 301 uses the measurement control unit 308 to search the measurement control information 316 using the message type that is the value of the element outside the normal range as a search key, and from the inspection device information 702 and the control content information 703 of the matching entry Information for specifying the inspection device and control contents are acquired (step S1201).
- the monitoring apparatus 301 causes the measurement control unit 308 to use the acquired control content information 703 as an instruction content, and transmits a change instruction to the inspection unit 32 of the inspection apparatus 30 indicated by the acquired inspection apparatus information 702 (step S30).
- step S1202 uses the measurement control unit 308 to search the measurement control information 316 using the message type that is the value of the element outside the normal range as a search key, and from the inspection device information 702 and the control content information 703 of the matching entry Information for specifying the inspection device and control contents are acquired (step S1201).
- the monitoring apparatus 301 causes
- the inspection apparatus 30 causes the inspection control unit 33 to change the transmission interval of the traffic report 34 from 60 sec.
- the inspection unit 32 is controlled to be 10 seconds.
- the monitoring device 301 searches the measurement setting information 315 using the measurement control unit 308 as a search key for the message type that is the value of the element returned from outside the normal range to the normal range, and checks the matching entry Information 702 and control content information 703 are acquired (step S1203).
- the monitoring apparatus 301 causes the measurement control unit 308 to use the acquired control content information 703 as an instruction content, and transmits a return instruction to the inspection unit 32 of the inspection apparatus 30 indicated by the acquired inspection apparatus information 702 (Step S ⁇ b> 3). S1203).
- control value of the inspection apparatus 30 is changed by a change instruction whose control content information 703 is “change of transmission interval (changed from 60 sec to 10 sec)”, and the element value returns within the normal range
- the monitoring apparatus 301 transmits a return instruction whose control content information 703 is “change in transmission interval (change from 60 sec to 10 sec)” by the measurement control unit 308.
- the inspection apparatus 30 interprets the return instruction control content information 703 by the inspection control unit 33 and returns the transmission interval of the traffic report 34 from 10 sec to 60 sec. Since the communication traffic of the network system 100 has returned to normal, the load on the inspection device 30 can be reduced by returning the transmission interval of the inspection device 30 to the original.
- each of the above-described configurations, functions, processing units, processing means, etc. may be realized in hardware by designing a part or all of them, for example, with an integrated circuit, and the processor realizes each function. It may be realized by software by interpreting and executing the program to be executed.
- Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, and an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, and a DVD.
- a storage device such as a memory, a hard disk, and an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, and a DVD.
- control lines and information lines indicate what is considered necessary for the explanation, and do not necessarily indicate all control lines and information lines necessary for mounting. In practice, it can be considered that almost all the components are connected to each other.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Bioinformatics & Computational Biology (AREA)
- Evolutionary Biology (AREA)
- Probability & Statistics with Applications (AREA)
- Life Sciences & Earth Sciences (AREA)
- Mathematical Physics (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
図1は、通信状態のモデリング例を示す説明図である。ネットワークシステム100は、複数(図1では例として5台)のノードNa~Ne(以下、総称してノードN)を有する。ノードNは、他のノードNと通信可能に接続される通信装置である。たとえば、ネットワークシステム100が、LTE(Long Term Evolution)(登録商標)が適用された通信システムである場合、ノードNaがeNB(evolved Node B)、ノードNbがMME(Mobility Management Entity)、ノードNcがHSS(Home Subscriber Server)、ノードNdがSGW(Serving Gateway)、ノードNeがPGW(PDN(Packet Data Network) Gateway)である。なお、同一種類のノードNが複数台存在してもよい。たとえば、ノードNa~Neは1台ずつ存在するが、複数台存在してもよい。
図2は、ネットワークシステム100内を流れるトラフィックのシーケンスと変換行列Aとの関係の一例を示す説明図である。図2において、シーケンス1は、ノードNaからのメッセージx1を起点として後続のメッセージy1~y3が順次生成されて後段のノードに出力され、最後のメッセージy3がノードNaに入力される。シーケンス2は、ノードNbからのメッセージx2を起点として後続のメッセージy4~y7が順次生成されて後段のノードに出力され、最後のメッセージy7がノードNdに入力される。シーケンス3は、ノードNeからのメッセージx3を起点として後続のメッセージy8が順次生成されてノードNeに入力される。
図3は、本実施例にかかる監視システムのシステム構成例を示すブロック図である。監視システム300は、監視対象であるネットワークシステム100内の通信トラフィックを観測して変換行列Aを作成し、変換行列を監視することにより、ネットワークシステム100の通信障害を検出するシステムである。
図8は、検査装置30および監視装置301(以下、装置800)のハードウェア構成例を示すブロック図である。装置800は、プロセッサ801、主記憶装置802、補助記憶装置803、ネットワーク11に接続するためのNIC(Network Interface Card)等のネットワークインタフェース装置804、キーボードやマウスなどの入力装置805、ディスプレイなどの出力装置806、および、それらの装置間を接続するバスなどの内部通信線807を備える。装置800は、たとえば、一般的なコンピュータにより実現される。
図9は、監視装置301による監視処理手順例を示すフローチャートである。監視装置301は、まず、集計部302によりトラフィック統計量集計処理を実行する(ステップS901)。具体的には、集計部302が検査装置30からトラフィック報告34を受信し、トラフィック報告34に含まれる検査項目や計測日時といった検査結果を取得する。そして、集計部302はメッセージタイプごとにメッセージ数を計数する。
Claims (12)
- 複数のノードを有し前記複数のノード間で通信可能な監視対象システムにおいて、前記監視対象システム内のノードが送受信する複数のメッセージを検査する検査装置と、前記検査装置からの検査結果を用いて、前記監視対象システムを監視する監視装置と、を有する監視システムであって、
前記監視装置は、
前記検査装置から受信する検査結果を用いて、前記ノードで送受信されるメッセージの種別ごとのメッセージ数を集計する集計処理と、
前記集計処理によって前記メッセージ数が集計されたメッセージの各々について、前記監視対象システムが送受信するメッセージのうち起点となる起点メッセージと、前記起点メッセージが前記複数のノードのいずれかのノードに与えられたことを契機として前記監視対象システム内で発生する発生メッセージとのいずれかに分類する分類処理と、
前記分類処理によって分類された前記起点メッセージのメッセージ数と前記発生メッセージのメッセージ数とに基づいて、前記起点メッセージと前記発生メッセージとの関係性を解析することにより、前記起点メッセージと前記発生メッセージとの関係性を示す行列を作成する解析処理と、
前記行列内の要素の値が正常範囲外になった場合に、前記監視対象システムの障害と判定する検出処理と、を実行する
ことを特徴とする監視システム。 - 請求項1に記載の監視システムであって、
前記解析処理では、前記監視装置は、計測日時が異なる複数の前記行列を作成し、
前記検出処理では、前記監視装置は、前記複数の行列における同一要素の値がいずれも前記正常範囲外の値になった場合に、前記監視対象システムの障害を検出する
ことを特徴とする監視システム。 - 請求項1に記載の監視システムであって、
前記監視装置は、
前記検出処理によって前記監視対象システムの障害が検出された場合、前記発生メッセージの種別を示すメッセージタイプと、前記ノードの種別を示すノードタイプと、前記ノードから前記メッセージを取得して検査する検査装置の識別情報と、を対応付けた計測設定情報から、前記正常範囲外となった要素に対応する特定の発生メッセージを生成した特定のノードの前記ノードタイプと、当該特定のノードから前記特定の発生メッセージを取得して検査する特定の検査装置の前記識別情報と、を取得することにより、異常発生個所を特定する特定処理を実行する
ことを特徴とする監視システム。 - 請求項1に記載の監視システムであって、
前記監視装置は、
前記検出処理によって前記監視対象システムの障害が検出された場合、前記ノードから前記メッセージを取得して検査する検査装置からの検査結果の送信間隔を変更するように制御する制御処理を実行し、
前記集計処理では、前記制御処理による変更後の送信間隔で送信されてくる前記検査結果を受信することにより、前記検査結果に基づいて、前記監視対象システム内の前記ノードから送信されるメッセージの種別ごとのメッセージ数を集計する
ことを特徴とする監視システム。 - 請求項1に記載の監視システムであって、
前記検査装置は、
前記監視対象システム内を流通するメッセージ群を受信する受信処理と、
前記受信処理によって受信されたメッセージ群を検査することにより、前記メッセージ群の各々のメッセージの種別を示すメッセージタイプと、前記受信処理による前記メッセージの受信日時と、前記メッセージの個数と、を含む検査結果を特定して、前記監視対象システムを監視する監視装置に所定の送信間隔で前記検査結果を送信する検査処理と、
前記監視装置からの制御指示により前記所定の送信間隔を制御する検査制御処理と、を実行する
ことを特徴とする監視システム。 - 請求項5に記載の監視システムであって、
前記検査装置は、
前記メッセージタイプに基づいて、前記メッセージ群のうち起点となる起点メッセージと、前記起点メッセージが前記複数のノードのいずれかのノードに与えられたことを契機として前記監視対象システム内で発生する発生メッセージとのいずれかに分類する分類処理を実行し、
前記検査処理では、前記プロセッサは、前記分類処理による分類結果を前記監視装置に送信する
ことを特徴とする監視システム。 - プログラムを実行するプロセッサと、前記プログラムを格納する記憶装置と、を有し、複数のノードを有し前記複数のノード間で通信可能な監視対象システムを監視する監視装置であって、
前記プロセッサは、
前記監視対象システムから受信する検査結果を用いて、前記ノードで送受信されるメッセージの種別ごとのメッセージ数を集計する集計処理と、
前記集計処理によって前記メッセージ数が集計されたメッセージの各々について、前記監視対象システムが送受信するメッセージのうち起点となる起点メッセージと、前記起点メッセージが前記複数のノードのいずれかのノードに与えられたことを契機として前記監視対象システム内で発生する発生メッセージとのいずれかに分類する分類処理と、
前記分類処理によって分類された前記起点メッセージのメッセージ数と前記発生メッセージのメッセージ数とに基づいて、前記起点メッセージと前記発生メッセージとの関係性を解析することにより、前記起点メッセージと前記発生メッセージとの関係性を示す行列を作成する解析処理と、
前記行列内の要素の値が、正常範囲外になった場合に、前記監視対象システムの障害と判定する検出処理と、を実行する
ことを特徴とする監視装置。 - 請求項7に記載の監視装置であって、
前記プロセッサは、
前記解析処理では、計測日時が異なる複数の前記行列を作成し、
前記検出処理では、前記複数の行列における同一要素の値がいずれも前記正常範囲外になった場合に、前記監視対象システムの障害を検出する
ことを特徴とする監視装置。 - 請求項7に記載の監視装置であって、
前記プロセッサは、
前記検出処理によって前記監視対象システムの障害が検出された場合、前記発生メッセージの種別を示すメッセージタイプと、前記ノードの種別を示すノードタイプと、前記ノードから前記メッセージを取得して検査する検査装置の識別情報と、を対応付けた計測設定情報から、前記正常範囲外となった要素に対応する特定の発生メッセージを生成した特定のノードの前記ノードタイプと、および当該特定のノードから前記特定の発生メッセージを取得して検査する特定の検査装置の前記識別情報と、を取得することにより、異常発生個所を特定する特定処理を実行する
ことを特徴とする監視装置。 - 請求項7に記載の監視装置であって、
前記プロセッサは、
前記検出処理によって前記監視対象システムの障害が検出された場合、前記ノードから前記メッセージを取得して検査する検査装置からの検査結果の送信間隔を変更するように制御する制御処理を実行し、
前記集計処理では、前記プロセッサは、前記制御処理による変更後の送信間隔で送信されてくる前記検査結果を受信することにより、前記検査結果に基づいて、前記監視対象システム内で送信されたメッセージごとのメッセージ数を集計する
ことを特徴とする監視装置。 - プログラムを実行するプロセッサと、前記プログラムを格納する記憶装置と、を有し、複数のノードを有し前記複数のノード間で通信可能な監視対象システムを検査する検査装置であって、
前記プロセッサは、
前記監視対象システム内を流通するメッセージ群を受信する受信処理と、
前記受信処理によって受信されたメッセージ群を検査することにより、前記メッセージ群の各々のメッセージの種別を示すメッセージタイプと、前記受信処理による前記メッセージの受信日時と、前記メッセージの個数と、を含む検査結果を特定して、前記監視対象システムを監視する監視装置に所定の送信間隔で前記検査結果を送信する検査処理と、
前記監視装置からの制御指示により前記所定の送信間隔を制御する検査制御処理と、を実行する
ことを特徴とする検査装置。 - 請求項11に記載の検査装置であって、
前記プロセッサは、
前記メッセージタイプに基づいて、前記メッセージ群のうち起点となる起点メッセージと、前記起点メッセージが前記複数のノードのいずれかのノードに与えられたことを契機として前記監視対象システム内で発生する発生メッセージとのいずれかに分類する分類処理を実行し、
前記検査処理では、前記プロセッサは、前記分類処理による分類結果を前記監視装置に送信する
ことを特徴とする検査装置。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016538167A JP6097889B2 (ja) | 2014-07-28 | 2015-03-18 | 監視システム、監視装置、および検査装置 |
US15/033,881 US20160283307A1 (en) | 2014-07-28 | 2015-03-18 | Monitoring system, monitoring device, and test device |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2014-152599 | 2014-07-28 | ||
JP2014152599 | 2014-07-28 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016017208A1 true WO2016017208A1 (ja) | 2016-02-04 |
Family
ID=55217113
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2015/058067 WO2016017208A1 (ja) | 2014-07-28 | 2015-03-18 | 監視システム、監視装置、および検査装置 |
Country Status (3)
Country | Link |
---|---|
US (1) | US20160283307A1 (ja) |
JP (1) | JP6097889B2 (ja) |
WO (1) | WO2016017208A1 (ja) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113225220A (zh) * | 2021-03-23 | 2021-08-06 | 深圳市东晟数据有限公司 | 网络分流器的测试组网***及其测试方法 |
Families Citing this family (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10536357B2 (en) | 2015-06-05 | 2020-01-14 | Cisco Technology, Inc. | Late data detection in data center |
EP3394785B1 (en) | 2015-12-24 | 2019-10-30 | British Telecommunications public limited company | Detecting malicious software |
WO2017109129A1 (en) * | 2015-12-24 | 2017-06-29 | British Telecommunications Public Limited Company | Software security |
US11201876B2 (en) | 2015-12-24 | 2021-12-14 | British Telecommunications Public Limited Company | Malicious software identification |
WO2017196216A1 (en) * | 2016-05-12 | 2017-11-16 | Telefonaktiebolaget Lm Ericsson (Publ) | A monitoring controller and a method performed thereby for monitoring network performance |
US11423144B2 (en) | 2016-08-16 | 2022-08-23 | British Telecommunications Public Limited Company | Mitigating security attacks in virtualized computing environments |
EP3500969A1 (en) | 2016-08-16 | 2019-06-26 | British Telecommunications Public Limited Company | Reconfigured virtual machine to mitigate attack |
EP3563242A1 (en) | 2016-12-28 | 2019-11-06 | Telefonaktiebolaget LM Ericsson (PUBL) | Dynamic management of monitoring tasks in a cloud environment |
US10541866B2 (en) * | 2017-07-25 | 2020-01-21 | Cisco Technology, Inc. | Detecting and resolving multicast traffic performance issues |
US11140055B2 (en) | 2017-08-24 | 2021-10-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and apparatus for enabling active measurements in internet of things (IoT) systems |
US11093310B2 (en) * | 2018-12-31 | 2021-08-17 | Paypal, Inc. | Flow based pattern intelligent monitoring system |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005216066A (ja) * | 2004-01-30 | 2005-08-11 | Internatl Business Mach Corp <Ibm> | 異常検出システム及びその方法 |
JP2006011683A (ja) * | 2004-06-24 | 2006-01-12 | Fujitsu Ltd | システム分析プログラム、システム分析方法及びシステム分析装置 |
JP2011113441A (ja) * | 2009-11-30 | 2011-06-09 | Fujitsu Ltd | メッセージ分類用属性選択装置,メッセージ分類用属性選択プログラムおよびメッセージ分類用属性選択方法 |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7568023B2 (en) * | 2002-12-24 | 2009-07-28 | Hewlett-Packard Development Company, L.P. | Method, system, and data structure for monitoring transaction performance in a managed computer network environment |
US20070255823A1 (en) * | 2006-05-01 | 2007-11-01 | International Business Machines Corporation | Method for low-overhead message tracking in a distributed messaging system |
US9319911B2 (en) * | 2013-08-30 | 2016-04-19 | International Business Machines Corporation | Adaptive monitoring for cellular networks |
EP2882141A1 (en) * | 2013-12-04 | 2015-06-10 | Exfo Inc. | Network test system |
US9967164B2 (en) * | 2014-09-02 | 2018-05-08 | Netscout Systems Texas, Llc | Methods and devices to efficiently determine node delay in a communication network |
US20160127180A1 (en) * | 2014-10-30 | 2016-05-05 | Splunk Inc. | Streamlining configuration of protocol-based network data capture by remote capture agents |
RO132010A2 (ro) * | 2015-12-22 | 2017-06-30 | Ixia, A California Corporation | Metode, sisteme şi suport citibil de calculator pentru diagnosticarea reţelei |
-
2015
- 2015-03-18 JP JP2016538167A patent/JP6097889B2/ja not_active Expired - Fee Related
- 2015-03-18 WO PCT/JP2015/058067 patent/WO2016017208A1/ja active Application Filing
- 2015-03-18 US US15/033,881 patent/US20160283307A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2005216066A (ja) * | 2004-01-30 | 2005-08-11 | Internatl Business Mach Corp <Ibm> | 異常検出システム及びその方法 |
JP2006011683A (ja) * | 2004-06-24 | 2006-01-12 | Fujitsu Ltd | システム分析プログラム、システム分析方法及びシステム分析装置 |
JP2011113441A (ja) * | 2009-11-30 | 2011-06-09 | Fujitsu Ltd | メッセージ分類用属性選択装置,メッセージ分類用属性選択プログラムおよびメッセージ分類用属性選択方法 |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113225220A (zh) * | 2021-03-23 | 2021-08-06 | 深圳市东晟数据有限公司 | 网络分流器的测试组网***及其测试方法 |
CN113225220B (zh) * | 2021-03-23 | 2022-03-18 | 深圳市东晟数据有限公司 | 网络分流器的测试组网***及其测试方法 |
Also Published As
Publication number | Publication date |
---|---|
JPWO2016017208A1 (ja) | 2017-04-27 |
JP6097889B2 (ja) | 2017-03-15 |
US20160283307A1 (en) | 2016-09-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP6097889B2 (ja) | 監視システム、監視装置、および検査装置 | |
US11252016B2 (en) | Anomaly detection and classification in networked systems | |
EP3379419B1 (en) | Situation analysis | |
US8634314B2 (en) | Reporting statistics on the health of a sensor node in a sensor network | |
KR102418969B1 (ko) | 딥러닝 기반 통신망 장비의 장애 예측 시스템 및 방법 | |
US8638680B2 (en) | Applying policies to a sensor network | |
US20150195154A1 (en) | Creating a Knowledge Base for Alarm Management in a Communications Network | |
US8560894B2 (en) | Apparatus and method for status decision | |
JP2022500963A (ja) | ネットワークのセキュリティモニタリング方法、ネットワークのセキュリティモニタリング装置及びシステム | |
JP2018513457A5 (ja) | ||
US20120026938A1 (en) | Applying Policies to a Sensor Network | |
US8874642B2 (en) | System and method for managing the performance of an enterprise application | |
JP2010511359A (ja) | ネットワーク異常検出のための方法と装置 | |
US11526422B2 (en) | System and method for troubleshooting abnormal behavior of an application | |
CN105610648A (zh) | 一种运维监控数据的采集方法及服务器 | |
US10291493B1 (en) | System and method for determining relevant computer performance events | |
US9479414B1 (en) | System and method for analyzing computing performance | |
US20200099570A1 (en) | Cross-domain topological alarm suppression | |
WO2015182629A1 (ja) | 監視システム、監視装置及び監視プログラム | |
US20130290476A1 (en) | Identifying Business Transactions from Traffic in an Enterprise Content Management System | |
JP2017211806A (ja) | 通信の監視方法、セキュリティ管理システム及びプログラム | |
US11265237B2 (en) | System and method for detecting dropped aggregated traffic metadata packets | |
CN112835780B (zh) | 一种业务检测方法及装置 | |
JP2017224181A (ja) | 監視対象システムを監視する分析装置 | |
JP6926646B2 (ja) | 事業者間一括サービス管理装置および事業者間一括サービス管理方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15826980 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15033881 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2016538167 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15826980 Country of ref document: EP Kind code of ref document: A1 |