Program monitoring system and program monitoring method

Abstract

To reduce operation for connecting to an environment where a customer program runs.SOLUTION: A program monitoring system that monitors a program for providing a service on a cloud includes: a parameter reception unit that receives specification of a value of a first parameter for monitoring the program; a parameter selection unit that selects a second parameter that is insufficient; a parameter request unit that requests the input of the value of the second parameter; and a program monitoring device that monitors the program for providing a service on a cloud by using the first parameter value received by the parameter reception unit and the second parameter value received by the parameter request unit.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a program monitoring system and a program monitoring method.

Background Art

[0002] In order to monitor a customer's service system operating on the cloud and provide a service for monitoring the occurrence of failures and the operating status, it is necessary to access the account operating the customer's service system from the account operating the monitoring system.

[0003] In Patent Document 1 (Japanese Patent Application Laid-Open No. 2017-68480), in a job management method in a cloud system, a step of inputting information regarding an instruction for defining an execution process of a business and an execution requirement including requirements for executing the execution process, and if there is no execution environment in the cloud system that conforms to the execution requirement, a step of creating an execution environment that conforms to the execution requirement in the cloud system, and a step of executing the execution process in an execution environment that conforms to the execution requirement are disclosed.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The invention of Patent Document 1 creates an environment necessary for executing a job script or a job network desired by a user on the cloud, and executes a desired job script or the like of the user in the created environment.

[0006] Therefore, the environment required to run job scripts, etc., is known, and there is no need to obtain parameters from others. Even if the environment is unknown, one can simply contact the developer or provider of the job script.

[0007] However, in order to provide a program monitoring service that monitors customer services on the cloud, it is necessary to build a simulated customer environment that accurately replicates the cloud environment in which the customer program runs, and to access the environment in which the customer program is running from the program monitoring device.

[0008] Therefore, it is desirable that customers understand why the parameters and other information they provide are necessary, and that they provide the necessary parameters smoothly. [Means for solving the problem]

[0009] The object of the present invention is a program monitoring system for monitoring a program that provides services on the cloud, and the object is solved by a program monitoring system comprising: a parameter receiving unit that accepts the specification of a value for a first parameter for monitoring the program; a parameter selection unit that selects a missing second parameter; a parameter requesting unit that requests input of a value for the second parameter; and a program monitoring device that monitors the program that provides services on the cloud using the value of the first parameter received by the parameter receiving unit and the value of the second parameter received by the parameter requesting unit. [Effects of the Invention]

[0010] According to the present invention, the work required to connect to the environment in which the customer program is running can be reduced. Other issues, configurations, and effects not mentioned above will be clarified by the following description of the embodiments. [Brief explanation of the drawing]

[0011] [Figure 1] This figure illustrates the system concept diagram in an embodiment of the present invention. [Figure 2] Customer Environment Connection Procedure in the Embodiment of the Present Invention [Figure 3] Example of System Configuration Diagram of Environment Construction Server in the Embodiment of the Present Invention [Figure 4] Example of Selection Parameter Table in the Embodiment of the Present Invention [Figure 5] Example of Component Parameter Table in the Embodiment of the Present Invention [Figure 6] Example of Component Template Corresponding Table in the Embodiment of the Present Invention [Figure 7] Example of Template Table in the Embodiment of the Present Invention [Figure 8] Example of Log Table in the Embodiment of the Present Invention [Figure 9] Example of Parameter Selection Screen in the Embodiment of the Present Invention [Figure 10] Example of Information Input Screen in the Embodiment of the Present Invention [Figure 11] Example of Reproducibility Display Screen in the Embodiment of the Present Invention [Figure 12] Example of Amendment Display Screen in the Embodiment of the Present Invention [Figure 13] Example of Parameter Temporary Setting Screen in the Embodiment of the Present Invention [Figure 14] Example of Flowchart Showing the Processing of Environment Construction Section in the Embodiment of the Present Invention [Figure 15] Example of Flowchart Showing the Processing of Reproducibility Calculation Section in the Embodiment of the Present Invention

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of the present invention will be described with reference to the drawings. In each of the drawings for explaining the embodiments, the same components are given the same names and reference numerals as much as possible, and the repeated explanations thereof are omitted.

[0013] The present invention is not limited to the embodiments described below, and includes various modifications and equivalent configurations within the scope of the appended claims. For example, the above-described embodiments have been described in detail for easy understanding of the present invention, and the present invention is not necessarily limited to those having all the configurations described.

[0014] In addition, the processing unit described in the embodiments may be realized in hardware by designing part or all of them, for example, by means of an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0015] The tables, regions, etc. described in the embodiments may be a database (DB) or data stored in the main memory.

Embodiment

[0016] FIG. 1 is a diagram for explaining a system conceptual diagram in an embodiment of the present invention.

[0017] An operator providing computer services used to prepare computer hardware such as a mainframe in its own computer room and provide computer services using the prepared computer hardware. In recent years, however, there are also many operators who provide computer services using a cloud environment such as AWS (Amazon Web Services) (AWS and Amazon Web Services are trademarks of Amazon Services LLC and its affiliates.).

[0018] When an operator prepares computer hardware in its own computer room and provides computer services, it was possible to monitor customer programs by installing a monitoring program for monitoring a program that provides computer services to the computer providing the computer services.

[0019] However, if the customer program is running in a cloud environment, installing a monitoring program in the customer's cloud environment and monitoring the customer program poses security risks.

[0020] Furthermore, installing monitoring programs in each cloud environment to monitor customer programs across multiple customer cloud environments consumes a significant amount of computing resources, and maintaining the monitoring programs themselves becomes difficult.

[0021] This embodiment describes an example of a program monitoring system using AWS, but it can also be implemented with other cloud services.

[0022] Therefore, as shown in Figure 1, when providing monitoring services, a monitoring service cloud environment is prepared, and the program monitoring device 7 is operated within the monitoring service cloud environment.

[0023] The program monitoring device 7 accesses the service system (customer program) 3 in the customer cloud environment 1 via the TGW (Transit Gateway) 6.

[0024] In this embodiment, access using TGW is used as an example, but the present invention can also be applied to access using VPN.

[0025] By adopting this method, it becomes possible to monitor multiple service systems with a single program monitoring device 7. The connection procedure in this case is explained in Figure 2.

[0026] Figure 2 shows the customer environment connection procedure in an embodiment of the present invention.

[0027] The customer terminal sends (1) CIDR (Classless Inter-Domain Routing) information, AWS account ID, and attachment ID. The monitoring service provider then (2) determines whether the received CIDR information is usable, and if it is determined to be usable, (3) uses the received information to build the customer connection environment 25.

[0028] The customer connection environment 25 includes a VPC (Virtual Private Cloud) 31, a subnet 32, and resources 33.

[0029] Furthermore, we will prepare customer connection accounts 24, and set up TGW29, VPN30, etc., which depend on the customer's AWS environment 23.

[0030] Here, we obtain customer approval (4) and connection permission, and then access resource 28 located in VPC 26, Subnet 27 of the customer's AWS environment 23.

[0031] However, each customer cloud environment is protected by various security systems, and accessing the service systems within a customer cloud environment requires various parameters. Therefore, it is necessary to obtain the necessary access parameters from the customer.

[0032] It is rare to receive all the necessary parameters from the customer, and if access is unavailable, it is necessary to inquire about the parameters from the customer each time.

[0033] In some cases, the customer's representative may not even know what the parameter value they were inquired about represents, and may be suspicious because they don't understand why providing that parameter is necessary to receive monitoring services from the customer service system.

[0034] In this situation, obtaining all the necessary parameter values ​​and other information from the customer takes time.

[0035] Therefore, when accessing the customer's cloud environment after receiving parameters from the customer, the system sets the provided parameters and attempts to connect by setting estimated parameter values ​​for parameters that have not been provided.

[0036] In this case, connection may not always be possible, so we will present the estimated parameter values ​​to the customer and ask them to send the correct parameter values.

[0037] This method, when used for upgrading customer service systems, or when a system engineer (SE) familiar with the customer's service system can deduce which parameters are incorrect and in some cases query the necessary parameter values.

[0038] However, in the case of first-time customers, there are often no system engineers familiar with the customer's service system. Therefore, a service system 9 is prepared in a simulated customer environment 8 as shown in Figure 1, and connection tests are performed.

[0039] To perform a connection test, the environment setup server 10 to which the setup terminal 11 is connected is prepared, the necessary parameters and their values ​​are estimated, and then a query is sent to the customer terminal 4 via the network 5.

[0040] Figure 3 shows an example of a system configuration diagram of an environment setup server in an embodiment of the present invention.

[0041] The environment setup server 10 consists of a computer equipped with a CPU 40, memory 41, external storage device 42, input / output unit 43, etc. The environment setup server 10 itself may also be located in the monitoring service cloud environment 2.

[0042] The memory 41 includes, as software modules, a parameter reception unit 44 for receiving parameter inputs, an environment construction unit 45 for creating a simulated customer environment 8, a log acquisition unit 46 for acquiring logs such as VPC flow logs obtained when connection tests are performed in the simulated customer environment 8, and a recall rate calculation unit 47 for calculating the recall rate, which indicates the degree to which the customer environment can be reproduced in the simulated customer environment 8.

[0043] Furthermore, the environment configuration unit 45 includes a parameter request unit 53 that requests parameters from the customer terminal, a parameter selection unit 54 that selects the requested parameters by referring to a component parameter correspondence TBL 49, etc., and a template selection unit 55 that selects a template for configuring the components. These software modules are executed on the CPU 40.

[0044] Memory 41 also stores a selection parameter table (selection parameter TBL) which stores the parameter values ​​selected to build the customer environment in the simulated customer environment 8.

[0045] The external storage device 42 includes a component parameter correspondence table (parameter correspondence table), a component template correspondence table (component template correspondence table), a template table (template table), and a log table (log table). Furthermore, it includes an input / output unit 43 for communication with customer terminals 4, etc.

[0046] Figure 4 shows an example of a selection parameter table in an embodiment of the present invention.

[0047] The selection parameter TBL48 stores the following associated items: part 60, parameter 61, selected parameter value 62, customer specification 63 indicating whether the parameter value was sent by the customer, and a template 64 for configuring the part.

[0048] When the customer-specified value is 1, the parameter value stored in the selected parameter value 62 is the one sent by the customer; if it is not 1, it indicates that it is an estimated value.

[0049] Figure 5 shows an example of a component parameter table in an embodiment of the present invention.

[0050] The component 60, parameter 61, TGW connection parameter value 72 (the parameter value when using TGW), VPN connection parameter value 73 (the parameter value when using VPN), and default value 74 (the default value of the parameter) are stored in association with each other.

[0051] Component parameters have values ​​other than their default values ​​that are used more frequently. By creating a column to register the most frequently used parameter values ​​over predetermined periods such as 6 months or 1 year, and displaying them as candidates when a parameter value is requested, the monitoring service can present candidates that are close to the parameter values ​​being used by the customer.

[0052] Furthermore, parameter values ​​often vary depending on the type of service provided by the customer receiving the monitoring service, as well as the communication method, security level, etc. For this reason, it may be advisable to create a column to register candidate parameter values ​​for each type of service provided by the customer.

[0053] By providing such candidate values, it becomes possible to suggest appropriate parameter values ​​that correspond to the services offered by the customer.

[0054] Figure 6 shows an example of a component template correspondence table in an embodiment of the present invention.

[0055] The component 60, the template 64 for configuring the component, and the parameters 61 used by the component are stored in association with each other.

[0056] Figure 7 shows an example of a template table in an embodiment of the present invention.

[0057] The component 60, the template 64 for configuring the component, and the parameters used by the component and the contents of the template 94 are stored in association with each other.

[0058] Figure 8 shows an example of a log table in an embodiment of the present invention.

[0059] The log contains logs related to multiple parts, and log 102, which is related to part 60, is stored in association with each other.

[0060] In this example, the communication logs in the first row, related to EC2 (Amazon Elastic Compute Cloud), are shown to be related to both EC2 and the Security Group. The communication logs in the third row, related to the VPC, are shown to be related to both the VPC and the Route Table.

[0061] The first line of the EC2 communication log shows a REJECT, which may indicate that the Security Group settings are incorrect.

[0062] Figure 9 shows an example of a parameter selection screen in an embodiment of the present invention.

[0063] The parameter selection screen 103 is displayed on the customer terminal 4, and message 150 is output, prompting the user to select a connection method.

[0064] In this example, there is a TGW button 151 to select TGW as the connection method, a VPN button 152 to select VPN, and an Other button 153 to select other connection methods.

[0065] Figure 10 shows an example of an information input screen in an embodiment of the present invention.

[0066] The information input screen 104 is displayed on the customer terminal 4 and outputs an information message to prompt the user to enter connection information. The required information varies depending on the connection method, but this example explains the case where the connection method is TGW.

[0067] For TGW, the user is required to enter their AWS account ID in area 155, their CIDR in area 157, and their attachment ID in area 157. After completing the input, pressing the submit button 158 sends the information to the environment setup server 10.

[0068] The information requested on this screen is mandatory; failure to provide it will make it difficult to offer monitoring services.

[0069] Figure 11 shows an example of a recall rate display screen in an embodiment of the present invention.

[0070] The recall rate display screen 105 is an example of a screen displayed on the customer terminal 4, with a map 112 of the simulated customer environment shown on the right side of the screen. The parameter settings of the simulated customer environment are displayed as map 112. Components enclosed by solid lines in map 112 are components whose settings have been completed.

[0071] Components enclosed in a dashed line can be configured if the parameters displayed in the required parameter field 111 are available. Components enclosed in a dotted line cannot be configured at this time.

[0072] In this embodiment, the setting status of the components is shown using solid lines, dotted lines, dashed lines, etc., but the color of the components may be changed based on the setting status, or the settings may be shown in a different manner, such as displaying configured and unconfigured components in a list format.

[0073] By selecting parameters in the required parameter field 111, you can check the change in the reproduction rate 114 of the simulated customer environment. After checking, press the parameter input button 113 on the left to send the new parameters to the service provider.

[0074] Figure 12 shows an example of a modified display screen in an embodiment of the present invention.

[0075] The suggested correction screen 106 is displayed on customer terminal 4. Components enclosed by dotted lines on the map 112 of the simulated customer environment on the right side of the screen are components that experienced failures during the connectivity check. In this way, not only can parameter errors and unset values ​​be discovered from the logs, but information about parameter errors and unset values ​​can also be obtained from errors during the connectivity check. The suggested correction 115 is displayed in the pane on the left side of the screen to prompt the customer to correct the parameter values.

[0076] Figure 13 shows an example of a parameter setting screen in an embodiment of the present invention.

[0077] The parameter setting screen 107 is a screen output to the construction terminal 11 used by the technician providing the monitoring service. It shows the unconfigured components enclosed by dotted lines on the simulated customer environment map 112.

[0078] The missing parameters column 116 displays the parameters that are missing from the component settings. In this example, it shows that the parameters for inbound rule 130, outbound rule 131, and instance type 132 are missing.

[0079] When a missing parameter is selected, the parameter candidate field 117 displays the parameter description 133 and the candidate parameter value 134 obtained by referring to the component parameter correspondence table 49.

[0080] The component parameter correspondence table 49 has a default value of 74 registered, and this value can be used as a candidate. However, registering the most frequently used parameter values ​​or parameter values ​​based on the type of program being monitored in the component parameter correspondence table 49 as candidates will allow for the suggestion of more appropriate parameter value candidates.

[0081] If the suggested parameter values ​​are deemed inappropriate, the next suggestion button 135 displays other options. When the OK button 136 is pressed, a map 112 of the simulated customer environment based on the displayed parameter value suggestions is shown.

[0082] Parameters that require direct input, such as IP addresses, can also be entered in parameter input field 118.

[0083] Figure 14 is an example flowchart showing the processing of the environment construction unit in an embodiment of the present invention.

[0084] If you choose not to build a simulated customer environment 8, but instead to inquire with the customer for the values ​​of a few missing parameters and use the parameter values ​​provided by the customer to connect to the customer cloud environment and monitor the customer program, you do not need to prepare all of the environment construction server configurations shown in Figure 3. You can simply run the parameter request unit 53, parameter selection unit 54, component parameter correspondence TBL 49, and log TBL 52 of the environment construction unit 45 in the same monitoring service cloud environment 2 as the program monitoring device 7.

[0085] In this case, the component that failed during connection to the customer environment should be identified in log TBL52, the necessary parameters for the identified component should be identified in component parameter-corresponding TBL, and the parameter values ​​of the identified parameters should be queried.

[0086] On the other hand, if you need to create a simulated customer environment and identify parameter values ​​on a large scale, you can create the simulated customer environment using the following procedure and then determine the necessary parameters.

[0087] The parameter reception unit 44 accepts the customer's selection of connection method on the parameter selection screen 103 (S1). The customer terminal 4 accepts information such as parameter values ​​on the information input screen 104 and stores it in the selected parameter TBL 48 along with the customer specification 63, which has a value "1" indicating that it is customer specification information (S2).

[0088] The parameter request unit 53 refers to the component parameter TBL49 and finds the component corresponding to the parameter (S3).

[0089] The template selection unit 55 refers to template TBL 51 and selects the template corresponding to the requested part (S4). Using the information of the requested part as a key, refer to the part parameter TBL49 to find any necessary unobtained parameters (S5).

[0090] The parameter selection unit 54 outputs default values ​​74, etc., corresponding to unobtained parameters obtained from the component parameter TBL 49, as candidate parameter values ​​to the parameter value candidate 134 on the parameter provisional setting screen 107 (S6).

[0091] The OK button 136 accepts the selection of parameter candidates (S7), and if a parameter is selected / input (S8), the selected parameter is registered in the selected parameter table (S10).

[0092] If no parameter is selected / input (S8), a default value such as 74 obtained from the component parameter table is registered in the selected parameter table (S9).

[0093] If processing has not been completed for all missing parameters required for component configuration, the process from S6 is repeated for the next missing parameter (S11).

[0094] If all unobtained parameters necessary for component configuration have been processed, the template registered in the selected parameters is executed with the registered parameter values ​​to build a simulated customer environment (S12).

[0095] Figure 15 is an example flowchart showing the processing of the recall calculation unit.

[0096] Connectivity is verified by performing a ping -c command or similar on the IP address of the simulated customer environment to obtain a response from the simulated customer environment (S20). If connectivity has not been confirmed, configure the necessary components and then run the program again in the simulated customer environment to perform connectivity checks.

[0097] If connectivity is confirmed, the VPC flow logs will be retrieved in the simulated customer environment (S22).

[0098] The communication results (REJECT / ACCEPT) obtained from the "communication logs obtained from the simulated customer environment" and the "communication logs obtained from the customer environment" are compared during the connectivity check (23).

[0099] next Recall rate = Number of matching logs / Total number of logs extracted from the simulated customer environment The recall rate is calculated using the following method. The numerator is the communication result that matches regardless of whether the communication result is REJECT or ACCEPT (S24).

[0100] In other words, if the communication result of the "communication log obtained from the customer environment" is REJECT, then if the communication result of the "communication log obtained from the simulated customer environment" is also REJECT, then it is determined that they match. [Explanation of symbols]

[0101] 1 Customer Cloud Environment, 2 Monitoring Service Cloud Environment, 3, 9 Service System, 4 Customer Terminal, 5 Network, 6 TGW, 7 Program Monitoring Device, 8 Simulated Customer Environment, 10 Environment Construction Server, 11 Construction Terminal, 21 Customer, 22 Monitoring Service Provider, 23 Customer's AWS Environment, 24 Customer Connection Account, 25 Customer Connection Environment, 40 CPU, 41 Memory, 42 External Storage Device, 43 Input / Output Unit, 44 Parameter Reception Unit, 45 Environment Construction Unit, 46 Log Acquisition Unit, 47 Recall Rate Calculation Unit, 48 Selection Parameter TBL, 49 Component Parameter Corresponding TBL, 50 Component Template Corresponding Table TBL, 51 Template TBL, 52 Log TBL, 53 Parameter Request Unit, 54 Parameter Selection Unit, 55 Template Selection Unit

Claims

1. A program monitoring system that monitors programs providing services on the cloud, A parameter receiving unit that accepts the specification of a value for a first parameter for monitoring the program, A parameter selection unit that selects a second parameter that is missing in order to monitor the aforementioned program, A parameter request unit that requests input for the value of the second parameter, A program monitoring system comprising a program monitoring device that monitors a program providing a service on the cloud using the value of a first parameter received by a parameter receiving unit and the value of a second parameter requested and received by a parameter requesting unit.

2. In the program monitoring system described in claim 1, An environment construction unit that uses the values ​​of the first and second parameters to build a simulated customer environment for the program, A log acquisition unit that acquires execution logs of the constructed simulated customer environment, The system includes a recall calculation unit that compares the execution logs of the customer environment in which the monitoring program is running to obtain information on the degree of reproduction of the simulated customer environment. A program monitoring system equipped with an output unit that outputs the desired reproduction accuracy information.

3. In the program monitoring system described in claim 2, The recall calculation unit seeks components corresponding to logs showing discrepancies between the customer environment and the simulated customer environment. The parameter request unit refers to a component parameter correspondence table that stores the correspondence between components and the parameters used in those components, and requests the parameter values ​​for the components used in the component corresponding to the log indicating a mismatch. A monitoring system for a program that outputs requests for parameter values ​​for components whose output unit has not been set to the customer terminal.

4. In the program monitoring system described in claim 3, The parameter selection unit refers to the component parameter correspondence table and finds candidate parameter values ​​for the component corresponding to the log indicating a mismatch. The parameter request unit is a program monitoring system that displays candidate parameters and requests parameter values ​​for components that correspond to logs indicating mismatches.

5. In the program monitoring system described in claim 3, The parameter request unit is a monitoring system for a program that displays a map of a simulated customer environment, showing the components corresponding to logs indicating mismatches with the configured components in different configurations.

6. In the program monitoring system described in claim 4, The parameter selection unit is a program monitoring system that selects default values ​​for parameters stored in the component parameter correspondence table as candidate parameter values ​​for parameters used in components that have not yet been set.

7. In the program monitoring system described in claim 4, The parameter selection unit is a program monitoring system that selects the most frequently used parameter value from the parameter correspondence table as a candidate parameter value for the component corresponding to the log indicating a mismatch.

8. In the program monitoring system described in claim 4, The parameter selection unit is a program monitoring system that selects parameter values ​​from a component parameter correspondence table that are likely to be used in the monitored program, as candidate parameter values ​​for the component corresponding to the log indicating a mismatch.

9. A method for monitoring programs that provide services on the cloud, The parameter receiving unit receives the value of the first parameter for monitoring the program, The parameter selection unit selects a second missing parameter to monitor the program, The parameter request unit requests input for the value of the second parameter. A program monitoring method in which a program monitoring device monitors a program that provides services on the cloud using the value of a first parameter received by a parameter receiving unit and the value of a second parameter requested and received by a parameter requesting unit.

Images