Operation management apparatus, operation management method, and operation management program

Patent metadata

Field	Value
Publication number	US-2025298681-A1
Application number	US-202418809735-A
Country	US
Kind code	A1
Filing date	Aug 20, 2024
Priority date	Mar 25, 2024
Publication date	Sep 25, 2025
Grant date	—

Abstract

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.

First claim

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
one or more processors; 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 predetermined 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 a user who uses the call destination service and the API used, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test.

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 specified user to be displayed in a specifiable manner.

5 . The operation management apparatus according to claim 4 , wherein the processor displays, for the specified user, an affected user who is a user having the failure occurred on the call destination service side and another 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
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 and 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 and a creation-related operation.

8 . The operation management apparatus according to claim 1 , wherein the processor notifies the specified 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 . 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 predetermined 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 a user who uses the call destination service and the API used, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test.

11 . 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 predetermined 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 a user who uses the call destination service and the API used, in a case where the failure on the call destination service side is reproduced as a result of the confirmation test.

Assignees

• Hitachi Ltd

Inventors

• Kitawaki Jun

Classifications

• G06F11/0751

  Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06) · CPC title

• G06F11/0772

  Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title

• G06F11/079

  Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36) · CPC title

• H04L67/02 Primary

  based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title

• G06F11/0709 Primary

  in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems · CPC title