JP6896035B2 - Monitoring system, monitoring SaaS provider, management device, and program - Google Patents

Description

The present invention relates to a monitoring system, a monitoring SaaS providing device, a management device, and a program.

An API service that provides various services using an API (Application Program Interface) has been known. (See, for example, Patent Document 1).
[Prior art literature]
[Patent Document]
[Patent Document 1] Japanese Unexamined Patent Publication No. 2018-165115

It is desirable to provide technology that can appropriately monitor API services.

According to the first aspect of the present invention, a monitoring system is provided. The monitoring system may include a first monitoring SaaS (Software as a Service) providing device having a first API monitoring unit that monitors API services via a network. The monitoring system may include a second monitoring SaaS provider having a second API monitoring unit that monitors the API service via the network. The first monitoring SaaS providing device may have a first SaaS monitoring unit that monitors the second monitoring SaaS providing device. The second monitoring SaaS providing device may have a second SaaS monitoring unit that monitors the first monitoring SaaS providing device.

The first notification SaaS providing device transmits notification data to a predetermined destination when a defect of the second monitoring SaaS providing device is detected by the first SaaS monitoring unit. Have a data transmitter. The second monitoring SaaS providing device sends notification data to a predetermined destination when a defect of the first monitoring SaaS providing device is detected by the second SaaS monitoring unit. It may have a data transmitter.

The second API monitoring unit responds to the detection of a defect in the first monitoring SaaS providing device that is executing the monitoring of the API service by the second SaaS monitoring unit. You may start monitoring. The first monitoring SaaS providing device issues a monitoring start instruction for starting monitoring of the API service in response to a problem in monitoring the API service by the first API monitoring unit. It may have an instruction transmitting unit to transmit to the SaaS providing device, and the second API monitoring unit may start monitoring the API service in response to receiving the monitoring start instruction.

The monitoring system may further include a management SaaS providing device having a monitoring management unit that manages the monitoring of the API service by the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring management unit may transmit information related to the monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring management unit may transmit parameters used for monitoring the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring management unit may transmit the start instruction, the pause instruction, and the completion instruction of the monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device.

The monitoring system is for managing the monitoring of the API service by the first monitoring SaaS providing device and the first plug-in for managing the monitoring of the API service by the second monitoring SaaS providing device. A management SaaS providing device having a monitoring management unit including a second plug-in may be further provided, and the monitoring management unit may provide the API service by the third monitoring SaaS providing device that monitors the API service via a network. It may have a plug-in adder that adds a third plug-in to manage the monitoring of.

The API service may have a plurality of APIs including the first API and an API gateway functioning as a gateway for the plurality of APIs, and the monitoring system monitors the first API. Based on the monitoring result receiving unit that receives the monitoring result of the first API and the monitoring result of the first API, it is detected that the maintenance has been started in the first API. Maintenance detection having a maintenance detection unit and a gateway control unit that shifts the mode for the first API in the API gateway to the maintenance mode when it is detected that maintenance has been started in the first API. Further equipment may be provided.

The monitoring system includes a monitoring result receiving unit that receives the monitoring result of the API service from the first API monitoring unit, an abnormality detection unit that detects an abnormality of the API service based on the monitoring result, and the above. A monitoring result analysis device having a warning data output unit that outputs warning data in response to the detection of the abnormality of the API service by the abnormality detection unit may be further provided.

The monitoring system includes a monitoring evaluation unit that evaluates the monitoring of the API service by the first monitoring SaaS providing device and the monitoring of the API service by the second monitoring SaaS providing device, and an evaluation by the monitoring evaluation unit. Based on the above, the priority determination unit that determines the priority of the first monitoring SaaS providing device and the second monitoring SaaS providing device, and the first monitoring SaaS providing device based on the above priority. A monitoring SaaS evaluation device having a monitoring content determining unit for determining the monitoring content of the API service and the monitoring content of the API service by the second SaaS providing device may be further provided.

According to the second aspect of the present invention, a SaaS providing device is provided. The SaaS providing device may include a SaaS monitoring unit that monitors other SaaS providing devices that are executing monitoring of API services via a network. The SaaS providing device may include an API monitoring unit that starts monitoring of the API service when a defect of another SaaS providing device is detected by the SaaS monitoring unit.

According to a third aspect of the present invention, a SaaS providing device is provided. The SaaS providing device may include an API monitoring unit that monitors API services via a network. The SaaS providing device may include a defect detection unit that detects that a defect occurs in the monitoring of the API service. The SaaS providing device may include an instruction transmitting unit that transmits a monitoring start instruction to start monitoring of the API service to another SaaS providing device in response to the detection by the defect detecting unit.

According to a fourth aspect of the present invention, a SaaS providing device is provided. The SaaS providing device monitors the API service by the first monitoring SaaS providing device that monitors the API service via the network and the second monitoring SaaS providing device that monitors the API service via the network via the network. It may have a monitoring management unit to manage. The monitoring management unit may transmit information related to the monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring management unit may transmit the parameters used for monitoring the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring management unit may transmit an API service monitoring start instruction, a pause instruction, and a completion instruction to the first monitoring SaaS providing device and the second monitoring SaaS providing device.

According to a fifth aspect of the present invention, a program for making a computer function as the SaaS providing device is provided.

According to a sixth aspect of the present invention, a management device is provided. The management device monitors the first plug-in for managing the monitoring of the API service via the network by the first monitoring SaaS providing device and the monitoring of the API service via the network by the second monitoring SaaS providing device. It may include a monitoring and management unit that includes a second plug-in for management. The monitoring management unit may have a plug-in addition unit that adds a third plug-in for managing the monitoring of the API service via the network by the third monitoring SaaS providing device.

According to a seventh aspect of the present invention, a management device is provided. The management device may include a monitoring result receiving unit that receives the monitoring result of the API from the monitoring SaaS providing device that monitors the API via the network. The management device may include a maintenance detection unit that detects that maintenance has been started in the API based on the monitoring result of the API. The management device may include a gateway control unit that shifts the mode for the API in the API gateway that functions as a gateway for a plurality of APIs including the API to the maintenance mode when it is detected that the maintenance has been started in the API. ..

According to an eighth aspect of the present invention, a management device is provided. The management device may include a monitoring result receiving unit that receives the monitoring result of the API service from the monitoring SaaS providing device that monitors the API service via the network. The management device may include an abnormality detection unit that detects an abnormality in the API service based on the monitoring result. The management device may include a warning data output unit that outputs warning data in response to the detection of an abnormality in the API service by the abnormality detection unit.

According to a ninth aspect of the present invention, a management device is provided. The management device may include a monitoring and evaluation unit that evaluates the monitoring of the API service via the network by the first monitoring SaaS providing device and the monitoring of the API service via the network by the second monitoring SaaS providing device. The management device may include a priority determination unit that determines the priority of the first monitoring SaaS providing device and the second monitoring SaaS providing device based on the evaluation by the monitoring evaluation unit. The management device may include a monitoring content determination unit that determines the monitoring content of the API service by the first monitoring SaaS providing device and the monitoring content of the API service by the second monitoring SaaS providing device based on the priority. ..

According to a tenth aspect of the present invention, a program for causing a computer to function as the management device is provided.

The outline of the above invention does not list all the necessary features of the present invention. Sub-combinations of these feature groups can also be inventions.

An example of the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the processing flow by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the monitoring status by the monitoring system 10 is shown schematically. An example of the functional configuration of the monitoring SaaS providing device 100 is schematically shown. An example of the hardware configuration of the computer 1200 that functions as the monitoring SaaS providing device 100, the management SaaS providing device 300, the maintenance detecting device 400, the monitoring result analysis device 500, or the monitoring SaaS evaluation device 600 is schematically shown.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the inventions that fall within the scope of the claims. Also, not all combinations of features described in the embodiments are essential to the means of solving the invention.

FIG. 1 schematically shows an example of the monitoring system 10. The monitoring system 10 according to the present embodiment monitors the API service 200 via the network 20. The network 20 may be any network, including, for example, the Internet and cloud networks.

The API service 200 is a service using API, and the type of service may be any type. Examples of the types of services include, but are not limited to, SMS (Short Message Service) distribution services, IoT (Internet of Things) management services, and key remote management services.

The monitoring system 10 includes a plurality of monitoring SaaS providing devices 100, and monitors the API service 200 by the plurality of monitoring SaaS providing devices 100. The monitoring SaaS providing device 100 is a device that provides monitoring SaaS for monitoring the API service 200.

The monitoring SaaS providing device 100 periodically or irregularly confirms whether or not the API service 200 is operating normally. The monitoring SaaS providing device 100 confirms whether or not the API service 200 is operating normally by, for example, transmitting an API request to the API service 200 periodically or irregularly.

The monitoring SaaS providing device 100 may confirm whether or not the API service 200 is operating normally by trying to use the service by the API service 200. For example, when the API service 200 provides the SMS distribution service, the monitoring SaaS providing device 100 transmits an SMS transmission request to the API service 200, and the processing such as "200 OK" from the API service 200 is normal. When the information indicating that the service has ended is received, it can be determined that the API service 200 is operating normally. Further, for example, when the API service 200 provides the IoT management service, the monitoring SaaS providing device 100 transmits a request for IoT device list information to the API service 200, and the API service 200 sends the IoT device list information. When it is received, it can be determined that the API service 200 is operating normally.

When the monitoring SaaS providing device 100 detects an abnormality in the API service 200, the monitoring SaaS providing device 100 may notify the person in charge terminal 30 of the person in charge 32 who is in charge of managing the API service 200 to that effect. The person in charge terminal 30 may be a mobile phone such as a smartphone, a tablet terminal, a PC (Personal Computer), or the like.

The monitoring SaaS providing device 100 according to the present embodiment monitors the API service 200 and also monitors another monitoring SaaS providing device 100. For example, the first monitoring SaaS providing device 100 monitors the API service 200 and the second monitoring SaaS providing device 100, and the second monitoring SaaS providing device 100 monitors the API service 200 and the first monitoring SaaS providing device 100. To monitor. In this way, the plurality of monitoring SaaS providing devices 100 according to the present embodiment mutually monitor each other. This makes it possible to automatically guarantee that monitoring is being continued correctly.

The plurality of monitoring SaaS providing devices 100 may play different roles. For example, the first monitoring SaaS providing device 100 mainly monitors the API service 200, and the second monitoring SaaS providing device 100 monitors the API service 200 as a sub. As a specific example, first, the first monitoring SaaS providing device 100 monitors the API service 200, and the second monitoring SaaS providing device 100 monitors the first monitoring SaaS providing device 100. The second monitoring SaaS providing device 100 starts monitoring the API service 200 when it detects the occurrence of a failure in the first monitoring SaaS providing device 100. As a result, the API service 200 is normally monitored only by the first monitoring SaaS providing device 100, so that efficiency can be improved by not performing duplicate monitoring, and the first monitoring SaaS providing device 100 fails. When such an event occurs, the monitoring of the API service 200 by the second monitoring SaaS providing device 100 can be started immediately.

The monitoring system 10 may further include a management SaaS providing device 300. The management SaaS providing device 300 manages a plurality of monitoring SaaS providing devices 100. The management SaaS providing device 300 sets parameters used for monitoring the API service 200 for each of a plurality of monitoring SaaS providing devices 100, and gives instructions such as execution of monitoring and stop of monitoring. .. Details of the processing of the management SaaS providing device 300 will be described later.

The monitoring system 10 may further include a maintenance detection device 400. The maintenance detection device 400 detects that maintenance has been monitored by the API service 200, and executes processing according to the detection result. Details of the processing of the maintenance detection device 400 will be described later.

The monitoring system 10 may further include a monitoring result analyzer 500. The monitoring result analysis device 500 receives the monitoring results of each of the plurality of monitoring SaaS providing devices 100 from each of the plurality of monitoring SaaS providing devices 100, and analyzes the monitoring results. Details of the processing by the monitoring result analyzer 500 will be described later.

The monitoring system 10 may further include a monitoring SaaS evaluation device 600. The monitoring SaaS evaluation device 600 evaluates the monitoring by each of the plurality of monitoring SaaS providing devices 100, and determines the monitoring content of each of the plurality of monitoring SaaS providing devices 100 according to the evaluation result. Details of the processing by the monitoring SaaS evaluation device 600 will be described later.

FIG. 2 schematically shows an example of the monitoring status by the monitoring system 10. FIG. 2 illustrates a case where the API service 200 is monitored by two monitoring SaaS providing devices 100 (monitoring SaaS providing device 102 and monitoring SaaS providing device 104), but the present invention is not limited to this, and three or more monitoring SaaS The API service 200 may be monitored by the providing device 100.

The monitoring SaaS providing device 102 monitors the API service 200. The monitoring SaaS providing device 102 transmits an API request to the API gateway 210 periodically or irregularly, for example. In the example shown in FIG. 2, the API gateway 210 transmits the API request as it is to the API 222, API 224, or API 226, or transmits the API request after performing a predetermined conversion. When the API gateway 210 receives the API response from the destination of the API request, the API gateway 210 transmits the API response as it is to the monitoring SaaS providing device 102, or transmits the API response after performing a predetermined conversion.

The monitoring SaaS providing device 102 determines whether or not the API service 200 is operating normally according to the reception status of the API response to the API request. For example, when the content of the received API response indicates an error, or when the monitoring SaaS providing device 102 does not receive the API response between the time when the API request is transmitted and the time when the predetermined time elapses. In addition, it can be determined that the API service 200 is not operating normally.

The monitoring SaaS providing device 104 monitors the API service 200 in the same manner as the monitoring SaaS providing device 102. The monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 may monitor the API service 200 without coordinating with each other, or may manage the API service 200 in cooperation with each other. For example, when they are not linked, each of the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 transmits an API request to the API gateway 210 at their respective timings. In the case of cooperation, for example, the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 alternately transmit API requests to the API gateway 210.

The monitoring SaaS providing device 102 further monitors the monitoring SaaS providing device 104. The monitoring SaaS providing device 102, for example, periodically or irregularly confirms whether or not the monitoring SaaS providing device 104 is operating normally. As a specific example, the monitoring SaaS providing device 102 makes an API call to the monitoring function of the monitoring SaaS providing device 104 periodically or irregularly, and whether or not the monitoring SaaS providing device 104 is operating normally based on the result. To judge. When the monitoring SaaS providing device 102 determines that the monitoring SaaS providing device 104 is not operating normally, the monitoring SaaS providing device 102 may notify the person in charge terminal 30 to that effect.

Similar to the monitoring of the monitoring SaaS providing device 104 by the monitoring SaaS providing device 102, the monitoring SaaS providing device 104 monitors the monitoring SaaS providing device 102. As a result, when the API service 200 is monitored by a plurality of monitoring SaaS providing devices 100, and if a problem occurs in the monitoring by at least one of the monitoring SaaS providing devices 100, the person in charge 32 or the like can quickly determine the situation. Can be notified and can contribute to early recovery.

FIG. 3 schematically shows an example of the monitoring status by the monitoring system 10. FIG. 3 illustrates a case where the API service 200 is monitored by two monitoring SaaS providing devices 100 (monitoring SaaS providing device 102 and monitoring SaaS providing device 104), but the present invention is not limited to this, and three or more monitoring SaaS are used. The API service 200 may be monitored by the providing device 100.

In the example shown in FIG. 3, the monitoring SaaS providing device 102 mainly monitors the API service 200, and the monitoring SaaS providing device 104 monitors the API service 200 as a sub. First, the monitoring SaaS providing device 102 monitors the API service 200. The monitoring method of the API service 200 may be the same as that of the monitoring SaaS providing device 102 in FIG.

The monitoring SaaS providing device 104 monitors the monitoring SaaS providing device 102. The monitoring SaaS providing device 104, for example, periodically or irregularly confirms whether or not the monitoring SaaS providing device 102 is operating normally. As a specific example, the monitoring SaaS providing device 104 makes an API call to the monitoring function of the monitoring SaaS providing device 102 periodically or irregularly, and whether or not the monitoring SaaS providing device 102 is operating normally based on the result. To judge.

When the monitoring SaaS providing device 104 determines that the monitoring SaaS providing device 102 is not operating normally, the monitoring SaaS providing device 104 starts monitoring of the API gateway 210. The monitoring SaaS providing device 104 may monitor the API service 200 in the same manner as the monitoring SaaS providing device 102. In this way, the API service 200 is monitored by the monitoring SaaS providing device 102, and when a failure or the like occurs in the monitoring SaaS providing device 102, the API service 200 is automatically monitored by the monitoring SaaS providing device 104. This makes it possible to continuously monitor the API service 200 while improving efficiency by not performing duplicate monitoring.

Instead of the monitoring SaaS providing device 104 monitoring the monitoring SaaS providing device 102, the monitoring SaaS providing device 102 may instruct the monitoring SaaS providing device 104 to monitor the API service 200. For example, the monitoring SaaS providing device 102 gives a monitoring start instruction to start monitoring the API service 200 in response to a situation in which the monitoring of the API service 200 cannot be continued, such as when a problem occurs in the monitoring of the API service 200. Is transmitted to the monitoring SaaS providing device 104. The monitoring SaaS providing device 104 starts monitoring the API service 200 in response to receiving the monitoring start instruction.

FIG. 4 schematically shows an example of the processing flow by the monitoring system 10. Here, the management SaaS providing device 300 sets the monitoring settings for the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104, and the monitoring SaaS providing device 102 mainly monitors the API service 200. The flow of processing by the monitoring system 10 when a problem occurs is shown.

In step 102 (the step may be abbreviated as S) 102, the person in charge 32 inputs the monitoring setting to the management SaaS providing device 300 by using the person in charge terminal 30. For example, the person in charge 32 inputs the parameters used for monitoring the API service 200 to the management SaaS providing device 300 by using the person in charge terminal 30.

In S104, the management SaaS providing device 300 reflects the monitoring setting to the monitoring SaaS providing device 102. In S106, the management SaaS providing device 300 reflects the monitoring setting to the monitoring SaaS providing device 104.

In S108, the monitoring SaaS providing device 102 transmits an API request to the API gateway 210. In S110, the API gateway 210 sends an API request to API 222. In S112, the API 222 sends an API response to the API gateway 210. In S114, the API gateway 210 transmits the API response to the monitoring SaaS provider 102. Here, the description will be continued assuming that the API response indicates an error.

In S116, the monitoring SaaS provider 102 detects an error in API 222. In S118, the monitoring SaaS providing device 102 transmits the error content to the person in charge terminal 30. In S120, the person in charge terminal 30 notifies the person in charge 32 that an error has occurred in API 222. In S122, the person in charge 32 confirms the error content received by the person in charge terminal 30 in S118. In S124, the person in charge 32 confirms the details of the error by accessing the monitoring SaaS providing device 102 via the person in charge terminal 30.

In S126, the monitoring SaaS providing device 104 executes an API call for the monitoring function of the monitoring SaaS providing device 102. Here, the description will be continued on the assumption that an error has occurred in the monitoring SaaS providing device 102. In S128, the monitoring SaaS providing device 104 detects an error in the monitoring SaaS providing device 102. The monitoring SaaS providing device 104 starts monitoring the API service 200 in response to the detection of the error.

In S130, the monitoring SaaS provider 104 transmits an API request to the API gateway 210. In S132, the API gateway 210 sends an API request to API 222. In S134, the API 222 sends an API response to the API gateway 210. In S136, the API gateway 210 transmits the API response to the monitoring SaaS provider 104. Here, the description will be continued assuming that the API response indicates an error.

In S138, the monitoring SaaS provider 104 detects an error in API 222. In S140, the monitoring SaaS providing device 104 transmits the error content to the person in charge terminal 30. In S142, the person in charge terminal 30 notifies the person in charge 32 that an error has occurred in API 222. In S144, the person in charge 32 confirms the error content received by the person in charge terminal 30 in S140. In S146, the person in charge 32 confirms the details of the error by accessing the monitoring SaaS providing device 104 via the person in charge terminal 30.

In S148, the monitoring SaaS providing device 104 executes an API call to the monitoring SaaS providing device 102 to confirm whether or not it has been restored. If it is determined that the recovery has not been performed, the monitoring SaaS providing device 104 continues to monitor the API service 200. When it is determined that the recovery has been made, the monitoring SaaS providing device 104 stops the monitoring of the API service 200, and the monitoring SaaS providing device 102 executes the monitoring of the API service 200.

FIG. 5 schematically shows an example of the functional configuration of the monitoring SaaS providing device 100. The monitoring SaaS providing device 100 includes an API monitoring unit 112, a SaaS monitoring unit 114, a notification data transmission unit 116, and an instruction transmission unit 118.

The API monitoring unit 112 monitors the API service 200. The API monitoring unit 112 may monitor a plurality of APIs via the API gateway 210. Further, the API monitoring unit 112 may monitor each of the plurality of APIs without going through the API gateway 210.

The SaaS monitoring unit 114 monitors another SaaS providing device 100. The SaaS monitoring unit 114 may monitor one other monitoring SaaS providing device 100. The SaaS monitoring unit 114 may monitor a plurality of other monitoring SaaS providing devices 100.

The notification data transmission unit 116 transmits notification data to a predetermined destination when a defect of another SaaS providing device 100 is detected by the SaaS monitoring unit 114. As the destination, for example, the e-mail address of the person in charge 32 and the like can be exemplified. The notification data may include the fact that a problem has occurred in the other monitoring SaaS providing device 100, the content of the problem, and the like.

The instruction transmission unit 118 transmits a monitoring start instruction for starting monitoring of the API service 200 to another monitoring SaaS providing device 100 in response to a problem in monitoring the API service 200 by the API monitoring unit 112.

FIG. 6 schematically shows an example of the monitoring status by the monitoring system 10. FIG. 6 illustrates a case where the API service 200 is monitored by two monitoring SaaS providing devices 100 (monitoring SaaS providing device 102 and monitoring SaaS providing device 104), but the present invention is not limited to this, and three or more monitoring SaaS The API service 200 may be monitored by the providing device 100.

In the example shown in FIG. 6, the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 each monitor the API service 200. In the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104, the monitoring SaaS providing device 102 may mainly monitor the API service 200, and the monitoring SaaS providing device 104 may monitor the API service 200 as a sub.

The management SaaS providing device 300 has a monitoring management unit 310 that manages the monitoring of the API service 200 by the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. The monitoring management unit 310 transmits information related to monitoring of the API service 200 to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. The monitoring management unit 310 transmits, for example, the information input by the person in charge 32 via the person in charge terminal 30 to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104.

The monitoring management unit 310 transmits, for example, parameters used for monitoring the API service 200 to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. For example, when the API token is required to monitor the API service 200, the monitoring management unit 310 transmits the API token to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. Further, when there is a condition that the request must include the date in order to monitor the API service 200, the monitoring management unit 310 sets the condition to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. And send.

Further, the monitoring management unit 310 transmits, for example, a monitoring start instruction, a pause instruction, an end instruction, and the like of the API service 200 to the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. For example, when the person in charge 32 knows the maintenance period of the API service 200, he / she may instruct not to execute the monitoring during the maintenance period. Further, when the person in charge 32 knows, for example, the period during which the use of the API service 200 is prohibited, the person in charge 32 may instruct not to execute the monitoring during the period.

FIG. 7 schematically shows an example of the monitoring status by the monitoring system 10. In the example shown in FIG. 7, the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 each monitor the API service 200. In the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104, the monitoring SaaS providing device 102 may mainly monitor the API service 200, and the monitoring SaaS providing device 104 may monitor the API service 200 as a sub.

The management SaaS providing device 300 has a monitoring management unit 310. The monitoring management unit 310 has a plug-in 302 for managing the monitoring of the API service 200 by the monitoring SaaS providing device 102, and a plug-in 304 for managing the monitoring of the API service 200 by the monitoring SaaS providing device 104.

The monitoring management unit 310 sets the monitoring SaaS providing device 102 for monitoring the API service 200 via the plug-in 302. Further, the monitoring management unit 310 sets the monitoring SaaS providing device 104 for monitoring the API service 200 via the plug-in 304.

The monitoring management unit 310 has a plug-in addition unit 320 for adding a plug-in. The plug-in addition unit 320 adds, for example, a plug-in 306 for managing the monitoring of the API service 200 by the monitoring SaaS providing device 106 that is newly added and monitors the API service 200. The plug-in addition unit 320 can add a plug-in for managing the monitoring of the API service 200 by the monitoring SaaS providing device to be further added. According to the monitoring system 10 shown in FIG. 7, the specification difference of each of the plurality of monitoring SaaS providing devices 100 is absorbed by the corresponding plug-in, so that the monitoring is performed without modification of the original monitoring management unit 310. It is possible to add a SaaS providing device.

FIG. 8 schematically shows an example of the monitoring status by the monitoring system 10. In the example shown in FIG. 8, the monitoring SaaS provider 102 monitors the API 222. The monitoring SaaS providing device 102 transmits the monitoring result of the API 222 to the maintenance detection device 400.

The maintenance detection device 400 includes a monitoring result receiving unit 402, a maintenance detection unit 404, and a gateway control unit 406. The monitoring result receiving unit 402 receives the monitoring result of the API 222 transmitted by the monitoring SaaS providing device 102. The monitoring result receiving unit 402 receives the monitoring result of the API 222 which is periodically or irregularly transmitted by the monitoring SaaS providing device 102.

The maintenance detection unit 404 detects that maintenance has been started in the API 222 based on the monitoring result received by the monitoring result receiving unit 402. When the maintenance detection unit 404 transmits an API request to the API 222 and receives data indicating that maintenance is in progress, such as "HTTP 503", the maintenance is started in the API 222. Judged as

Further, the maintenance detection unit 404 detects that the maintenance has been started in the API 222, for example, based on the information collected in advance. As a specific example, the maintenance detection unit 404 acquires and analyzes a plurality of response contents when an API request is transmitted to the API 222 while the API 222 is performing maintenance. As a result, the maintenance detection unit 404 acquires the pattern of the response content when the API 222 is performing maintenance. Then, when the maintenance detection unit 404 determines that the pattern of the response content when the API request is transmitted to the API 222 a plurality of times matches the pattern of the response content during maintenance, the API 222 performs maintenance. Is determined to be performed. As a result, it is possible to determine whether or not the API 222 is under maintenance even when the data such as "HTTP 503" is not returned as a response even though the API 222 is under maintenance.

Further, for example, the maintenance detection unit 404 analyzes the date and time when the API 222 has been unable to connect and has timed out, and the response content as statistical data by machine learning, and the error generated in the API 222 is due to maintenance or a failure. Determine if it is a thing.

When the maintenance detection unit 404 detects that the maintenance has been started in the API 222, the gateway control unit 406 shifts the mode for the API 222 in the API gateway 210 to the maintenance mode.

If the API gateway 210 knows that the API 222 is under maintenance, the API gateway 210 shifts to the maintenance mode by itself and notifies the API request from the outside that the API 222 is under maintenance. can do. However, the API gateway 210 cannot always know that the API 222 is under maintenance. For example, in response to an inquiry from the API gateway 210, if the API 222 returns "HTTP 503", it can be grasped that maintenance is in progress, but if it returns "HTTP 500", it cannot be grasped.

On the other hand, according to the maintenance detection device 400 according to the present embodiment, the maintenance detection unit 404 detects that the maintenance has been started in the API 222, and the gateway control unit 406 changes the mode for the API 222 in the API gateway 210 to the maintenance mode. Will be migrated. As a result, even in a situation where the API gateway 210 cannot grasp that the maintenance has been started in the API 222, the API gateway 210 can be shifted to the maintenance mode, and the API gateway 210 can respond to an inquiry from the outside. It is possible to notify that API 222 is under maintenance.

The monitoring SaaS providing device 102 continues to monitor the API 222 while the API 222 is being maintained, and transmits the monitoring result to the maintenance detection device 400. When the maintenance detection device 400 detects that the maintenance of the API 222 is completed based on the monitoring result, the maintenance detection device 400 may release the maintenance mode for the API 222 in the API gateway 210.

FIG. 9 schematically shows an example of the monitoring status by the monitoring system 10. In the example shown in FIG. 9, the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 each monitor the API service 200. In the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104, the monitoring SaaS providing device 102 may mainly monitor the API service 200, and the monitoring SaaS providing device 104 may monitor the API service 200 as a sub. The monitoring SaaS providing device 102 and the monitoring SaaS providing device 104 transmit the monitoring result to the monitoring result analyzer 500 periodically or irregularly, respectively.

The monitoring result analysis device 500 includes a monitoring result receiving unit 502, an abnormality detection unit 504, and a warning data output unit 506. The monitoring result receiving unit 502 receives the monitoring result of the API service 200 transmitted by each of the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104.

The abnormality detection unit 504 detects an abnormality in the API service 200 based on the monitoring result received by the monitoring result receiving unit 502. The abnormality detection unit 504, for example, determines the content of the API request transmitted to the API service 200 for monitoring and the content of the API response from the API service 200 by each of the monitoring SaaS providing device 102 and the monitoring SaaS providing device 104. Analyze as statistical data. Then, the abnormality detection unit 504 detects an abnormality in the API service 200 when the API response to the API request tends to be different from the usual one.

For example, when targeting the API service 200 in which the content of the API response to the API request becomes the same value each time when operating normally, the abnormality detection unit 504 indicates that the content of the API response is different. In addition, it detects anomalies. Further, for example, the abnormality detection unit 504 detects an abnormality when the time from receiving the API request to transmitting the API response differs from normal time by a statistically significant range. Further, for example, the abnormality detection unit 504 detects an abnormality when the data size of the API response is different from the normal time by a statistically significant width. By adopting such a detection method, the abnormality detection unit 504 is different from the normal monitoring service that detects an abnormality by referring to the HTTP status code, and is normal on the HTTP status code. Alternatively, it is possible to detect an abnormality in the API service 200 for which no explicit error condition is set.

FIG. 10 schematically shows an example of the monitoring status by the monitoring system 10. In the example shown in FIG. 10, each of the plurality of monitoring SaaS providing devices 100 monitors the API service 200. The plurality of monitoring SaaS providing devices 100 take turns monitoring the API service 200 at predetermined periods such as every hour, every day, every week, and so on. It includes a monitoring evaluation unit 602, a priority determination unit 604, and a monitoring content determination unit 606.

The monitoring evaluation unit 602 evaluates the monitoring of the API service 200 by each of the plurality of monitoring SaaS providing devices 100. The monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on the service operating time. The monitoring and evaluation unit 602, for example, raises the evaluation as the service operating time becomes longer.

The monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on the response time. For example, the monitoring evaluation unit 602 raises the evaluation as the response time becomes shorter.

The monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on the error detection accuracy. For example, the higher the error detection accuracy, the higher the evaluation of the monitoring evaluation unit 602.

The monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on the monitoring call success rate. The monitoring evaluation unit 602, for example, raises the evaluation as the success rate of the monitoring call increases.

The monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on a plurality of the service operating time, the response time, the error detection accuracy, and the monitoring call success rate. Further, the monitoring evaluation unit 602 may evaluate the monitoring SaaS providing device 100 based on other than these.

The priority determination unit 604 determines the priority of the plurality of monitoring SaaS providing devices 100. The priority determination unit 604 determines the priority of the plurality of monitoring SaaS providing devices 100 according to the manual setting by the person in charge 32, for example. Further, the priority determination unit 604 determines the priority of the plurality of monitoring SaaS providing devices 100 based on the evaluation by the monitoring evaluation unit 602. The priority determination unit 604 increases the priority of the plurality of monitoring SaaS providing devices 100 in descending order of evaluation, for example.

The monitoring content determination unit 606 determines the monitoring content of the API service 200 by each of the plurality of monitoring SaaS providing devices 100 based on the priority determined by the priority determination unit 604. For example, the monitoring content determination unit 606 monitors the API service 200 by the monitoring SaaS providing device 100 when a failure occurs in any one of the monitoring SaaS providing devices 100. When it becomes impossible, the monitoring SaaS providing device 100 having the highest priority among the remaining monitoring SaaS providing devices 100 is made to monitor the API service 200 instead of the monitoring SaaS providing device 100.

Further, the monitoring content determination unit 606 determines, for example, the monitoring execution time of each of the plurality of monitoring SaaS providing devices 100 based on the priority. For example, when each of the five monitoring SaaS providing devices 100 takes turns monitoring the API service 200 every day, the monitoring time of the monitoring SaaS providing device 100 having the highest priority is set to 4 days, and then the priority. The monitoring time of the high-priority monitoring SaaS providing device 100 is 3 days, the monitoring time of the next highest priority monitoring SaaS providing device 100 is 2 days, and the monitoring time of the next highest priority monitoring SaaS providing device 100 is 1 day. The monitoring time of the lowest priority monitoring SaaS provider 100 is determined in half a day. As a result, the monitoring SaaS providing device 100 having a high priority can perform monitoring for a long time, and the reliability of the overall monitoring can be improved.

FIG. 11 schematically shows an example of a hardware configuration of a computer 1200 that functions as a monitoring SaaS providing device 100, a management SaaS providing device 300, a maintenance detecting device 400, a monitoring result analysis device 500, or a monitoring SaaS evaluation device 600. A program installed on the computer 1200 causes the computer 1200 to function as one or more "parts" of the device according to the present embodiment, or causes the computer 1200 to perform an operation associated with the device according to the present embodiment or the one or more. A plurality of "parts" can be executed and / or a computer 1200 can be made to execute a process according to the present embodiment or a stage of the process. Such a program may be executed by the CPU 1212 to cause the computer 1200 to perform a specific operation associated with some or all of the blocks of the flowcharts and block diagrams described herein.

The computer 1200 according to this embodiment includes a CPU 1212, a RAM 1214, and a graphic controller 1216, which are connected to each other by a host controller 1210. The computer 1200 also includes input / output units such as a communication interface 1222, a storage device 1224, a DVD drive 1226, and an IC card drive, which are connected to the host controller 1210 via the input / output controller 1220. The DVD drive 1226 may be a DVD-ROM drive, a DVD-RAM drive, or the like. The storage device 1224 may be a hard disk drive, a solid state drive, or the like. The computer 1200 also includes a legacy I / O unit such as a ROM 1230 and a keyboard, which are connected to the I / O controller 1220 via an I / O chip 1240.

The CPU 1212 operates according to the programs stored in the ROM 1230 and the RAM 1214, thereby controlling each unit. The graphic controller 1216 acquires the image data generated by the CPU 1212 in a frame buffer or the like provided in the RAM 1214 or itself so that the image data is displayed on the display device 1218.

Communication interface 1222 communicates with other electronic devices via a network. The storage device 1224 stores programs and data used by the CPU 1212 in the computer 1200. The DVD drive 1226 reads a program or data from a DVD-ROM 1227 or the like and provides it to the storage device 1224. The IC card drive reads the program and data from the IC card and / or writes the program and data to the IC card.

The ROM 1230 stores in it a boot program or the like executed by the computer 1200 at the time of activation and / or a program depending on the hardware of the computer 1200. The input / output chip 1240 may also connect various input / output units to the input / output controller 1220 via a USB port, a parallel port, a serial port, a keyboard port, a mouse port, and the like.

The program is provided by a computer-readable storage medium such as a DVD-ROM 1227 or an IC card. The program is read from a computer-readable storage medium, installed in a storage device 1224, RAM 1214, or ROM 1230, which is also an example of a computer-readable storage medium, and executed by the CPU 1212. The information processing described in these programs is read by the computer 1200 and provides a link between the program and the various types of hardware resources described above. The device or method may be configured to implement the operation or processing of information in accordance with the use of the computer 1200.

For example, when communication is executed between the computer 1200 and an external device, the CPU 1212 executes a communication program loaded in the RAM 1214, and performs communication processing on the communication interface 1222 based on the processing described in the communication program. You may order. Under the control of the CPU 1212, the communication interface 1222 reads and reads transmission data stored in a transmission buffer area provided in a recording medium such as a RAM 1214, a storage device 1224, a DVD-ROM 1227, or an IC card. The data is transmitted to the network, or the received data received from the network is written to the reception buffer area or the like provided on the recording medium.

Further, the CPU 1212 makes the RAM 1214 read all or necessary parts of a file or a database stored in an external recording medium such as a storage device 1224, a DVD drive 1226 (DVD-ROM1227), an IC card, etc. Various types of processing may be performed on the data of. The CPU 1212 may then write back the processed data to an external recording medium.

Various types of information such as various types of programs, data, tables, and databases may be stored in recording media and processed. The CPU 1212 describes various types of operations, information processing, conditional judgment, conditional branching, unconditional branching, and information retrieval described in various parts of the present disclosure with respect to the data read from the RAM 1214. Various types of processing may be performed, including / replacement, etc., and the results are written back to the RAM 1214. Further, the CPU 1212 may search for information in a file, a database, or the like in the recording medium. For example, when a plurality of entries each having an attribute value of the first attribute associated with the attribute value of the second attribute are stored in the recording medium, the CPU 1212 is the first of the plurality of entries. The attribute value of the attribute of is searched for the entry that matches the specified condition, the attribute value of the second attribute stored in the entry is read, and the first attribute that satisfies the predetermined condition is selected. You may get the attribute value of the associated second attribute.

The program or software module described above may be stored on a computer 1200 or in a computer-readable storage medium near the computer 1200. Also, a recording medium such as a hard disk or RAM provided in a dedicated communication network or a server system connected to the Internet can be used as a computer-readable storage medium, thereby allowing the program to be transferred to the computer 1200 via the network. provide.

The blocks in the flowchart and block diagram of this embodiment may represent a stage of the process in which the operation is performed or a "part" of the device responsible for performing the operation. Specific stages and "parts" are supplied with dedicated circuits, programmable circuits supplied with computer-readable instructions stored on computer-readable storage media, and / or computer-readable instructions stored on computer-readable storage media. It may be implemented by the processor. Dedicated circuits may include digital and / or analog hardware circuits, and may include integrated circuits (ICs) and / or discrete circuits. Programmable circuits include logical products, logical sums, exclusive logical sums, negative logical products, negative logical sums, and other logical operations, such as, for example, field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), and the like. , Flip-flops, registers, and reconfigurable hardware circuits, including memory elements.

The computer-readable storage medium may include any tangible device capable of storing instructions executed by the appropriate device, so that the computer-readable storage medium having the instructions stored therein is in a flow chart or block diagram. It will be equipped with a product that contains instructions that can be executed to create means for performing the specified operation. Examples of the computer-readable storage medium may include an electronic storage medium, a magnetic storage medium, an optical storage medium, an electromagnetic storage medium, a semiconductor storage medium, and the like. More specific examples of computer-readable storage media include floppy (registered trademark) disks, diskettes, hard disks, random access memory (RAM), read-only memory (ROM), and erasable programmable read-only memory (EPROM or flash memory). , Electrically Erasable Programmable Read Only Memory (EEPROM), Static Random Access Memory (SRAM), Compact Disc Read Only Memory (CD-ROM), Digital Versatile Disc (DVD), Blu-ray® Disc, Memory Stick , Integrated circuit cards and the like may be included.

Computer-readable instructions are assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, or object-oriented programming such as Smalltalk, JAVA®, C ++, etc. Contains either source code or object code written in any combination of one or more programming languages, including languages and traditional procedural programming languages such as the "C" programming language or similar programming languages. Good.

Computer-readable instructions are used to generate means for a general-purpose computer, a special-purpose computer, or the processor of another programmable data processing device, or a programmable circuit, to perform an operation specified in a flowchart or block diagram. General purpose computers, special purpose computers, or other programmable data processing locally or via a local area network (LAN), a wide area network (WAN) such as the Internet, etc. to execute the computer readable instructions. It may be provided in the processor of the device or in a programmable circuit. Examples of processors include computer processors, processing units, microprocessors, digital signal processors, controllers, microcontrollers and the like.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It will be apparent to those skilled in the art that various changes or improvements can be made to the above embodiments. It is clear from the description of the claims that such modified or improved forms may also be included in the technical scope of the present invention.

The order of execution of each process such as operation, procedure, step, and step in the device, system, program, and method shown in the claims, specification, and drawings is particularly "before" and "prior to". It should be noted that it can be realized in any order unless the output of the previous process is used in the subsequent process. Even if the scope of claims, the specification, and the operation flow in the drawings are explained using "first", "next", etc. for convenience, it means that it is essential to carry out in this order. It's not a thing.

10 monitoring system, 20 networks, 30 person in charge terminal, 32 person in charge, 100, 102, 104, 106 monitoring SaaS providing device, 112 API monitoring unit, 114 SaaS monitoring unit, 116 notification data transmission unit, 118 instruction transmission unit, 200 API service, 210 API gateway, 222, 224, 226 API, 300 management SaaS provider, 302, 304, 306 plug-in, 310 monitoring management unit, 320 plug-in addition unit, 400 maintenance detection device, 402 monitoring result receiver, 404 Maintenance detection unit, 406 Gateway control unit, 500 Monitoring result analyzer, 502 Monitoring result receiving unit, 504 Abnormality detection unit, 506 Warning data output unit, 600 Monitoring SaaS evaluation device, 602 Monitoring evaluation unit, 604 Priority determination unit, 606 Monitoring content determination unit 1200 computer, 1210 host controller, 1212 CPU, 1214 RAM, 1216 graphic controller, 1218 display device, 1220 input / output controller, 1222 communication interface, 1224 storage device, 1226 DVD drive, 1227 DVD-ROM, 1230 ROM, 1240 I / O chip

Claims (23)

It ’s a monitoring system,
A first monitoring SaaS provider having a first API monitoring unit that monitors API services via a network, and
It is provided with a second monitoring SaaS providing device having a second API monitoring unit that monitors the API service via a network.
The first monitoring SaaS providing device has a first SaaS monitoring unit that monitors the second monitoring SaaS providing device.
The second monitoring SaaS providing device is a monitoring system including a second SaaS monitoring unit that monitors the first monitoring SaaS providing device. The first monitoring SaaS providing device is
The first aspect of the present invention has a first notification data transmission unit that transmits notification data to a predetermined destination when a defect of the second monitoring SaaS providing device is detected by the first SaaS monitoring unit. Described monitoring system. The second monitoring SaaS providing device is
The second aspect of the present invention has a second notification data transmission unit that transmits notification data to a predetermined destination when a defect of the first monitoring SaaS providing device is detected by the second SaaS monitoring unit. Described monitoring system. The second API monitoring unit responds to the detection of a defect in the first monitoring SaaS providing device that is executing the monitoring of the API service by the second SaaS monitoring unit. The monitoring system according to any one of claims 1 to 3, wherein the monitoring of the above is started. The first monitoring SaaS providing device issues a monitoring start instruction for starting monitoring of the API service in response to a problem in monitoring the API service by the first API monitoring unit. It has an instruction transmitter that transmits to the SaaS provider,
The monitoring system according to any one of claims 1 to 3, wherein the second API monitoring unit starts monitoring of the API service in response to receiving the monitoring start instruction. The first monitoring SaaS providing device and any one of claims 1 to 5 further comprising a management SaaS providing device having a monitoring management unit for managing the monitoring of the API service by the second monitoring SaaS providing device. Described monitoring system. The monitoring system according to claim 6, wherein the monitoring management unit transmits information related to monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The monitoring system according to claim 7, wherein the monitoring management unit transmits parameters used for monitoring the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The seventh aspect of claim 7, wherein the monitoring management unit transmits a start instruction, a pause instruction, and a completion instruction of the monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. Monitoring system. A first plug-in for managing the monitoring of the API service by the first monitoring SaaS providing device, and a second plug-in for managing the monitoring of the API service by the second monitoring SaaS providing device. Further equipped with a management SaaS providing device having a monitoring management unit including
The monitoring management unit has a plug-in addition unit that adds a third plug-in for managing the monitoring of the API service by the third monitoring SaaS providing device that monitors the API service via the network. The monitoring system according to any one of items 1 to 5. The API service has a plurality of APIs including the first API and an API gateway functioning as a gateway of the plurality of APIs.
The monitoring system
A monitoring result receiving unit that receives the monitoring result of the first API from the first API monitoring unit that monitors the first API, and a monitoring result receiving unit.
Based on the monitoring result of the first API, a maintenance detection unit that detects that maintenance has been started in the first API, and a maintenance detection unit.
A maintenance detection device including a gateway control unit that shifts the mode for the first API in the API gateway to the maintenance mode when it is detected that the maintenance has been started in the first API is further provided. The monitoring system according to any one of claims 1 to 10. A monitoring result receiving unit that receives the monitoring result of the API service from the first API monitoring unit, and
An abnormality detection unit that detects an abnormality in the API service based on the monitoring result,
The invention according to any one of claims 1 to 10, further comprising a monitoring result analyzer having a warning data output unit that outputs warning data in response to the detection of an abnormality in the API service by the abnormality detection unit. Described monitoring system. A monitoring evaluation unit that evaluates the monitoring of the API service by the first monitoring SaaS providing device and the monitoring of the API service by the second monitoring SaaS providing device.
A priority determination unit that determines the priority of the first monitoring SaaS providing device and the second monitoring SaaS providing device based on the evaluation by the monitoring evaluation unit.
Based on the priority, it has a monitoring content determination unit that determines the monitoring content of the API service by the first monitoring SaaS providing device and the monitoring content of the API service by the second monitoring SaaS providing device. The monitoring system according to any one of claims 1 to 12, further comprising a monitoring SaaS evaluation device. SaaS providing device,
A SaaS monitoring unit that monitors other SaaS providers that monitor API services via the network,
A SaaS providing device including an API monitoring unit that starts monitoring of the API service when a defect of the other SaaS providing device is detected by the SaaS monitoring unit. SaaS providing device,
The API monitoring unit that monitors API services via the network,
A defect detection unit that detects that a defect occurs in the monitoring of the API service, and
A SaaS providing device including an instruction transmitting unit that transmits a monitoring start instruction to start monitoring of the API service to another SaaS providing device in response to detection by the defect detecting unit. SaaS providing device,
Monitoring that manages the monitoring of the API service by the first monitoring SaaS providing device that monitors the API service via the network and the second monitoring SaaS providing device that monitors the API service via the network. A SaaS providing device including a management unit. The SaaS providing device according to claim 16, wherein the monitoring management unit transmits information related to monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The SaaS providing device according to claim 17, wherein the monitoring management unit transmits parameters used for monitoring the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. The 17th aspect of the present invention, wherein the monitoring management unit transmits a start instruction, a pause instruction, and a completion instruction of the monitoring of the API service to the first monitoring SaaS providing device and the second monitoring SaaS providing device. SaaS providing device. A program for causing a computer to function as a SaaS provider according to any one of claims 14 to 19. A first plug-in for managing the monitoring of the API service via the network by the first monitoring SaaS providing device, and a second plug-in for managing the monitoring of the API service via the network by the second monitoring SaaS providing device. Equipped with a monitoring management unit including a second plug-in
The monitoring management unit is a management device having a plug-in addition unit that adds a third plug-in for managing the monitoring of the API service via the network by the third monitoring SaaS providing device. A monitoring evaluation unit that evaluates the monitoring of the API service via the network by the first monitoring SaaS providing device and the monitoring of the API service via the network by the second monitoring SaaS providing device.
A priority determination unit that determines the priority of the first monitoring SaaS providing device and the second monitoring SaaS providing device based on the evaluation by the monitoring evaluation unit.
Based on the priority, the monitoring content determination unit for determining the monitoring content of the API service by the first monitoring SaaS providing device and the monitoring content of the API service by the second monitoring SaaS providing device is provided. Management device. A program for causing a computer to function as the management device according to claim 21 or 22.

Images