Operation management apparatus, operation management method, and operation management program
In an operation management apparatus that manages an operation of a system that provides a service requesting processing from an external service via an application programming interface (API), a storage device stores test data for causing the external service to execute processing via the API, the external service that a user uses through the service, and a correspondence relationship between the external service and the API that the user uses the processor is configured to detect whether or not a failure has occurred on the external service side, confirm whether or not the failure on the call destination service side is reproduced via an API used when the failure occurred, using the test data in a case of detecting the failure and specify a user who uses the external service and the API used, in a case where the failure on the external service side is reproduced.
1 . An operation management apparatus that manages an operation of a system that provides a plurality of users with a provision service that requests processing from one or more call destination services via an application programming interface (API), the operation management apparatus comprising:
a processor; and
a storage device,
wherein
the storage device stores test data for causing the call destination service to execute processing via the API, a call destination service that a user uses through the provision service, and a correspondence relationship between the call destination service and an API that the user uses, and
the processor:
detects whether or not a failure has occurred on a call destination service side in the provision service for a particular user,
executes, in a case of detecting the failure on the call destination service side, a confirmation test for confirming whether or not the failure on the call destination service side is reproduced via an API used when the failure occurred, using the test data, and
specifies each affected user and each potentially affected user, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test,
wherein the processor identifies:
the particular user for whom the failure was detected;
each affected user currently using the call destination service and API combination where the failure is reproduced; and
each potentially affected user who uses the call destination service and API combination where the failure is reproduced, and
wherein the particular user, each affected user, and each potentially affected user are each among the plurality of users.
2 . The operation management apparatus according to claim 1 , wherein the call destination service is an external service provided by a third party different from a management entity of the system.
3 . The operation management apparatus according to claim 1 , wherein the processor detects that a call destination service that the user uses by a provision service has been changed, and causes the storage device to store a call destination service of a detected change destination as a call destination service that the user uses.
4 . The operation management apparatus according to claim 1 , wherein the processor causes the particular user, each affected user, and each potentially affected user to be displayed in a specifiable manner.
5 . The operation management apparatus according to claim 4 , wherein the processor displays the particular user, each affected user, and each potentially affected user in a distinguishable manner.
6 . The operation management apparatus according to claim 1 , wherein the storage device stores an operation type to a call destination service by an API, and
wherein the processor specifies an operation type by the API used and displays information specifying the API used in association with the user in a display aspect in accordance with the specified operation type.
7 . The operation management apparatus according to claim 6 , wherein the processor displays information specifying an API of which an operation type to a call destination service is an update-related operation or a delete-related operation in a more emphasized manner than information specifying an API of which an operation type to a call destination service is a reference-related operation or a creation-related operation, wherein update-related operation and delete-related operation include operations that modify or remove data in the call destination service, wherein reference-related operation and creation-related operation include operations that retrieve or add data without modifying existing data, and wherein a single operation type may perform multiple functions.
8 . The operation management apparatus according to claim 1 , wherein the processor notifies the particular user, each affected user, and each potentially affected user of information regarding occurrence of a failure.
9 . The operation management apparatus according to claim 1 , wherein, in a case where a predetermined period or less has passed since performance of the confirmation test for a call destination service in which the failure has occurred, the processor uses a result of the confirmation test performed within the predetermined period without executing a confirmation test.
10 . The operation management apparatus according to claim 1 , wherein the processor monitors a log file output by a microservice that calls the call destination service to detect the failure, and
wherein the log file includes a uniform resource locator (URL) of the call destination service, a user identifier, and a status code returned from the call destination service.
11 . The operation management apparatus according to claim 1 , wherein the processor distinguishes between an internal error occurring within the system and an external error occurring on the call destination service side based on the result of the confirmation test, and
wherein the processor specifies all users using a microservice that calls the call destination service when the internal error is detected.
12 . The operation management apparatus according to claim 1 , wherein the storage device stores a microservice table that identifies each microservice calling the call destination service, and
wherein the processor uses the microservice table to determine which microservice is affected by the failure on the call destination service side.
13 . The operation management apparatus according to claim 1 , wherein the processor updates a current usage status in the storage device to indicate whether each user is currently using the call destination service and API combination where the failure is reproduced, and
wherein the processor identifies each affected user based on the current usage status indicating current use of the call destination service and API combination.
14 . An operation management method by an operation management apparatus that manages an operation of a system that provides a plurality of users with a provision service that requests processing from one or more call destination services via an application programming interface (API), wherein the operation management apparatus:
stores test data for causing the call destination service to execute processing via the API, a call destination service that a user uses through the provision service, and a correspondence relationship between the call destination service and an API that the user uses,
detects whether or not a failure has occurred on a call destination service side in the provision service for a particular user,
executes, in a case of detecting the failure on the call destination service side, a confirmation test for confirming whether or not the failure on the call destination service side is reproduced via an API used when the failure occurred, using the test data, and
specifies each affected user and each potentially affected user, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test,
wherein the operation management apparatus identifies:
the particular user for whom the failure was detected;
each affected user currently using the call destination service and API combination where the failure is reproduced; and
each potentially affected user who uses the call destination service and API combination where the failure is reproduced, and
wherein the particular user, each affected user, and each potentially affected user are each among the plurality of users.
15 . An operation management program for causing a computer to execute management of an operation of a system that provides a plurality of users with a provision service that requests processing from one or more call destination services via an application programming interface (API),
wherein the computer stores test data for causing the call destination service to execute processing via the API, a call destination service that a user uses through the provision service, and a correspondence relationship between the call destination service and an API that the user uses, and
the computer is caused to:
detect whether or not a failure has occurred on a call destination service side in the provision service for a particular user,
execute, in a case of detecting the failure on the call destination service side, a confirmation test for confirming whether or not the failure on the call destination service side is reproduced via an API used when the failure occurred, using the test data, and
specify each affected user and each potentially affected user, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test,
wherein the computer identifies:
the particular user for whom the failure was detected;
each affected user currently using the call destination service and API combination where the failure is reproduced; and
each potentially affected user who uses the call destination service and API combination where the failure is reproduced, and
wherein the particular user, each affected user, and each potentially affected user are each among the plurality of users.